﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / SQL Server 2005 / SQL Server 2005 Security  / Passwords - case sensitive in Login using SQL Server Authentication / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Mon, 20 May 2013 03:13:28 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Passwords - case sensitive in Login using SQL Server Authentication</title><link>http://www.sqlservercentral.com/Forums/Topic657395-359-1.aspx</link><description>By default SQL Server is case insensitive with respect to the login. So unless you've chosen a collation when you installed SQL Server that is case sensitive, it doesn't matter if the app logs in as sa, SA, sA, or Sa. The password is always case sensitive. If you're application doesn't take case sensitivity into account with respect to password, does it treat it as all lowercase or uppercase? If so, make the password conform to that.</description><pubDate>Fri, 30 Apr 2010 12:35:51 GMT</pubDate><dc:creator>K. Brian Kelley</dc:creator></item><item><title>RE: Passwords - case sensitive in Login using SQL Server Authentication</title><link>http://www.sqlservercentral.com/Forums/Topic657395-359-1.aspx</link><description>[quote][b]K. Brian Kelley (2/15/2009)[/b][hr]No. While the login name was case-insensitive if your SQL Server has a case-insensitive collation, the password is always case sensitive. This is because of the hashing algorithm used.[/quote]I understand your reply but i wonder if you can help.We recently migrated from Windows SBS 2000 to Windows SBS 2008 as well as SQL Server 2000 to SQL server 2008.We use an in house software which, when developed, didn't take into consideration the CASE SENSITIVITY for the login (user: sa pass: aBc123) since SQL server 2000 didn't care for the sesnsitivity. The developer realizes now that it was poor software design on his part and is trying to fix it. In the meanwhile I was wondering if we can run an SQL Query on the SQL SERVER 2008 to tell it not to care for the sensitivity of the user 'sa'.Something along the lines  of:[code="sql"]ALTER LOGIN sa PASSWORD = 'aBc123' COLLATE SQL_Latin1_General_CP1_CI_AS[/code]I know this is not a proper SQL query, but can you suggest anything?</description><pubDate>Thu, 29 Apr 2010 13:45:27 GMT</pubDate><dc:creator>ebayemails123</dc:creator></item><item><title>RE: Passwords - case sensitive in Login using SQL Server Authentication</title><link>http://www.sqlservercentral.com/Forums/Topic657395-359-1.aspx</link><description>Thank you for your help!</description><pubDate>Fri, 20 Feb 2009 15:58:03 GMT</pubDate><dc:creator>Decommissioned_Account_02</dc:creator></item><item><title>RE: Passwords - case sensitive in Login using SQL Server Authentication</title><link>http://www.sqlservercentral.com/Forums/Topic657395-359-1.aspx</link><description>No. While the login name was case-insensitive if your SQL Server has a case-insensitive collation, the password is always case sensitive. This is because of the hashing algorithm used.</description><pubDate>Sun, 15 Feb 2009 15:58:00 GMT</pubDate><dc:creator>K. Brian Kelley</dc:creator></item><item><title>Passwords - case sensitive in Login using SQL Server Authentication</title><link>http://www.sqlservercentral.com/Forums/Topic657395-359-1.aspx</link><description>Hi,In SQL Server 2005, Logins using SQL Server Authentication are case sensitive (even if you remove the “Enforce password policy” option in the login prosperity).Is there a way to turn this feature off in a Login or on all Logins on the server?Example:Login: DavidPassword: BLUE Is there a way that Password: BLUE and Password: blue to both work?Thanks,David</description><pubDate>Sun, 15 Feb 2009 14:04:24 GMT</pubDate><dc:creator>Decommissioned_Account_02</dc:creator></item></channel></rss>