When I configured the System DSN, seems no matter what case I entered the password in, they all worked. Does that mean, password is not case sensitive on SQL Server?

Thanks very much for the information, Andy. Since I'm not quite familiar with MS SQL server, it will take me more time and learning to get your message fully digested.

That depends on the collation or sort order of your server. Do a
sp_helpsort. If the server sort order is case-insensitive, then your
passwords are as well. Nice feature of SQL 2000, read this for more info.
Remember the default collation of SQL (1252) is not case-sensitive

http://www.microsoft.com/sql/techinfo/tips/administration/casesensitive.asp


--
*******************************************************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@NOMORESPAM.yahoo.com

Please remove NOMORESPAM before replying.

Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.

This posting is provided "as is" with no warranties
and confers no rights.

*******************************************************************
[quoted text, click to view]
password in, they all worked. Does that mean, password is not case
sensitive on SQL Server?
[quoted text, click to view]

Here's a great suggestion to, go Windows Authentication. If you, your
users, your applications and company can handle it, it is a great way to
secure SQL. Heck, SQL 2000 SP 3a tries to even force it. Gets you closer
to the goal of single sign-on, but then of course you have to worry about
everything being right so you don't get trusted connection login errors.

BTW, by sending that article about the sort order, I think that is
ridiculous. If you have databases with sort orders other than what the
master database has, you really have to watch it with temp tables and other
items in the tempdb. I've seen many a stored procedure have to be rewritten
because some database got attached to a server with a different sort order,
which caused a problem with the stored procedure making temp tables.

--
*******************************************************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@NOMORESPAM.yahoo.com

Please remove NOMORESPAM before replying.

Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.

This posting is provided "as is" with no warranties
and confers no rights.

*******************************************************************
[quoted text, click to view]
password in, they all worked. Does that mean, password is not case
sensitive on SQL Server?
[quoted text, click to view]