| ctcrmcou on Oct 28, 2004 at 12:00:30 PM No I don't believe it is possible. The references, indexes, etc. that are created throughout take case sensitivity into account when the keys are created. It's not just about the data. And SQL Server creates MANY MANY tables of its own for administrative purposes - all of which would be affected.
Now if you want to just store a user's password in case sensitive fashion for a client application or something, then a simple approach would be to delimit each character with a code:
"MyPassWord" stored as "/M\y/P\a\s\s/W\o\r\d". / denotes the next character is uppercase \ denotes lower case. I would have used u and l but to hard to read here. Here's why:
Case sensitive server: "select * from usertable where password = '" + Password + "'"
The user's case sensitivity is compared exactly, which is ideal.
Non-case sensitive server: you must parse the supplied password to insert the case delimiters, then it will work:
"select * from usertable where password = '" + DelimitedPassword + "'"
Now since the passwords are stored in the database with the delimiters coded in, you will get the match assuming the case sensitive password is correct.
But if your looking at database user passwords, then you're out of luck. Export your databases, reinstall, reimport your databases.
| 
Case-sensitive SQL Server instance