March 10, 2004 at 2:24 pm
I find this site to be a great knowledge resource for all things SQL Server.
However, one of my biggest frustrations is that many of the articles written by contributors, as well as script resources, are not written correctly to account for case-sensitive sql collations. Example: in one section a script refers to a temp table as ##DBNAMES and in the same script refers again with ##dbnames.
Numerous times, I have downloaded/copied a great sounding script - either from the resource library or from an article that was highly rated, only to find that it completely falls apart with syntax errors, etc when compiling on one of my case-sensitive instances.
I realize BINARY sort orders are not nearly as popular as with 6.x and below versions of SQL, but there certainly is still a business justification for using case-sensitivity on sql environments.
Not sure how to go about fixing this, but I think it would be helpful to at least have contributors start validating on different collations or put some sort of disclaimer that many of these resources will not work on anything but a vanilla install.
Comments, thoughts?
March 11, 2004 at 4:00 am
A quick way that I used to use this scripts on Case Sensitive Servers
was to load the script in Query Analyser
CTRL + A (select ALL)
CTRL + SHIFT + L (lowercase all)
as most evrery system tables / object is in lower case.
exceptions are scripts calling INFORMATION_VIEW , sp_MSprocs... etc.
those needs manual change.
March 14, 2004 at 7:39 pm
Given that the majority of us don't use case sensitive servers I'm not sure it would make sense to require that all scripts meet that standard. I agree if you're running case sensitive it's extra work to get everything to fixed, but at least the core process is there and you're just doing cleanup.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply