Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
manzoor_mustafa
Starting Member
6 Posts |
 Posted - 2009-08-31 : 11:28:19
|
| Hi I have many Stored Procedures in SQL Server 2008 Compatibility level 100 where I am using LTRIM to return empty strings but due to triming of empty strings the return value is modified to null due to which I am unable to run an application. Please provide any resolution for this issue so that without modifying all the SPs where LTRIM is used, I can change and remove this incompatibility issue. Please provide the solution asap.Thanks |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
rohitkumar
Constraint Violating Yak Guru
472 Posts |
Posted - 2009-08-31 : 14:17:05
|
| was this ever working before? |
 |
|
|
manzoor_mustafa
Starting Member
6 Posts |
Posted - 2009-09-07 : 02:27:25
|
quote:
Originally posted by manzoor_mustafa
Hi For DB migration to SQL SERVER 2008, i need to know how to handle the incompactibilty of "LTRIM" function. In SQL SERVER 6.5, LTRIM('') return NULL where as in 2008, EMPTY STRING is returned (from SQL SERVER 2000 onwards, EMPTY STRING is returned). This had been already documented in "sp_dbcmptlevel" topic:http://msdn.microsoft.com/en-us/library/aa259649(SQL.80).aspxCurently, i am manually looking into all objects where LTRIM or RTRIM are used and adding a condition to return NULL(existing business logic checks for NULL value to perform some action at DB level itself).Is there any work around or a better approach to address this issue(as there more than 800 DB objects - SPs, User Functions to be checked)? Thanks
|
|
|
|
|
|
|
Steps to remove