Dear Professionals,

I would appreciate if anyone can give me pros and cons of SQL Server
COLLATION Settings at database or column levels.

Thanks

Using case-sensitive collation at the database level is a royal PIA. It
means that every single object, every single TSQL statement must be correct
case-wise. Don't do it. On the other hand, having a specific column set to
case-sensitive often makes sense.

--
__________________________________________________ ________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker’s Guide to Visual Studio and SQL Server (7th Edition)
http://betav.com http://betav.com/blog/billva
__________________________________________________ __________________________________________



"Rogers" <Rogers (AT) discussions (DOT) microsoft.com> wrote

Rogers,

William Vaughn told you why you should not.

So, is there any good reason to use a database (or server level) Case
Sensitive collation? Yes, if you are creating code to be deployed on
servers and/or databases where you have no control over the collation. (I
have a couple of BINARY collation servers that cause me some problems.)

Developing in Case Sensitive will ensure that you go through the pain of
correcting every last case problem before you deploy to other servers. (On
the other hand, it will not catch the less likely problem of two items named
the same except for case. E.g. tables named Drought and DrOught.)

FWIW,
RLF


"Rogers" <Rogers (AT) discussions (DOT) microsoft.com> wrote