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 |
|
MikeA
Starting Member
1 Post |
 Posted - 2011-05-17 : 10:49:46
|
| I have an established database schema with many dozen stored procedures all working great. However, I recently needed to deploy the database to a case sensitive SQL Server. I am now running into several errors because of case sensitivity. Is there any tool that can assist with resolving the T-SQL case issues or do I need to manually go through and resolve any issues. Most common seems to be declared variables which are later referenced with the wrong case… e.g. Declare @Type.. and then referring to that variable as @type.Any “automated” ways to resolve these types of issues?Thx,Mike |
|
|
nigelrivett
Master Smack Fu Yak Hacker
3385 Posts |
Posted - 2011-05-17 : 11:13:57
|
| You could maybe use a code formatter.The problem might be you can end up with two references that shuold be the same object. I woud do this manually and use a source control system so you can keep a record of changes.A bigger problem might be that your SPs might expect to be able to compare data that it espects to be the same but is now considered different - e.g. any strings that are defined in code.==========================================Cursors are useful if you don't know sql.SSIS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
|
|
|
TSQL Issues with case sensitive collation