SQL Server Performance Forum – Threads Archive

Password case sensitive…

Did someones know a way to deactivate the password case sensitive option?
I have this collation and i don’t understand why my password need to be case sensitive: Latin1-General, case-insensitive, accent-sensitive, kanatype-insensitive, width-insensitive for Unicode Data, SQL Server Sort Order 52 on Code Page 1252 for non-Unicode Data Thanks
Pat

---

When you define Latin1-….., is for user databases.
System databases, in witch password are stored, is case sensitive. So, as far I know, you can’t deactivate case sensitive option for password.
Luis Martin
Moderator
SQL-Server-Performance.com One of the symptoms of an approaching nervous breakdown is the belief that one’s work is terribly important
Bertrand Russell
All postings are provided “AS IS” with no warranties for accuracy.

---

I think, sort-order can not be cheanged once you installed SQL Server 2000. If you want to change, I think you need to re-install SQL Server and you have to select required sort-order. -Johnson

---

Hi,<br />you can change the collation refer * collations, changing * in BOL.<br /><br /><br />[<img src=’/community/emoticons/emotion-1.gif’ alt=’‘ />]<br />Regards<br /><br />Hemantgiri S. Goswami<br />[email protected]<br />"Humans don’t have Caliber to PASS TIME , Time it self Pass or Fail Humans" – by Hemantgiri S. Goswami<br />

---

hi, I think, I got something from BOL: —————
Changing Collations After Setup
When you set up SQL Server 2000, it is important to use the correct collation settings. You can change collation settings after running Setup, but you must rebuild the databases and reload the data. It is recommended that you develop a standard within your organization for these options. Many server-to-server activities can fail if the collation settings are not consistent across servers. ————— -Johnson

---

Hi ya, passwords in sql server for sql user accounts are always case sensitive. SQL creates an encrypted format for the password and stores that in the table, this encryption is sensitive to case changes Cheers
Twan

---

Once the default collation has been selected during installation and for new data you can define new collation, use BCP to take affect of new collation on database — table — column wide.
Satya SKJ
Contributing Editor & Forums Moderator
http://www.SQL-Server-Performance.Com
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.

---

Satya,
So how we will query for the combination of both data, which means, data related to the old collation and the data related to new collation in one query? -Johnson

---

Hi,<br />for that please refer * copying data, between different collations * in BOL .<br /><br /><img src=’/community/emoticons/emotion-1.gif’ alt=’‘ /><br />Regards<br /><br />Hemantgiri S. Goswami<br />[email protected]<br />"Humans don’t have Caliber to PASS TIME , Time it self Pass or Fail Humans" – by Hemantgiri S. Goswami<br />

---

Is your problem that you’re getting errors when you try to join on columns of different collations? Add the phrase COLLATE <collationname> | DATABASE_DEFAULT immediately after the non-matching column. Same thing in WHERE clauses

---

Are you sure the passwords are case sensitive? They don’t appear to be in either my personal edition installation or developer edition installation? I created a sql identified id dtipton and assigned it a password of ISAAC. I can successfully connect via Query Analyzer and EM using dtipton/ISAAC or dtipton/isaac. The case doesn’t seem to matter. Is there something I’m missing? Both instances are using the default Latin collation.

---

Passwords in a case-insensitive SQL Server are converted to uppercase before being stored or used. Passwords in a case-sensitive SQL Server are not converted to uppercase. Because of this difference, passwords originally encrypted on a case-sensitive server and later transferred to a case-insensitive server cannot be used unless all alphabetic characters in the password are uppercase. Satya SKJ
Contributing Editor & Forums Moderator
http://www.SQL-Server-Performance.Com
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.

---

Thanks for the clarification Satya.

---

Thanks every body for the answer, it’s now more clear for me [<img src=’/community/emoticons/emotion-1.gif’ alt=’‘ />]

---

Thanks Satya, for the clarification about the sort-order functionality and about the collation as well. I didn’t try to use that, the reason was, I didn’t face such scenario till now. But my doubt was how we will get the data from a database with two collation in one query. I got the logic how to apply, Let me try that and if any issue, surely come here. Thanks once again
-Johnson

---

]]>