SQL2005 enforce sql logins to using Windows password Policy.

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

mecn - 19 Jul 2007 17:29 GMT

Hi,

IF I check both CHECK_POLICY and CHECK_EXPIRATION on in sql2005. It will
enable sql logins to use WINdows2003 AD password policy?
If AD configured case sensitive. Sql logins will be case sensitive as well
even sql2002 sort order is 52.
If an application is use ODBC connection to the sql2005, Do I need to change
the ODBC driver to native ODBC or something?

Thanks

Reply to this Message

Bob Beauchemin - 19 Jul 2007 22:46 GMT

Inline:

> Hi,
>
> IF I check both CHECK_POLICY and CHECK_EXPIRATION on in sql2005. It will
> enable sql logins to use WINdows2003 AD password policy?

If the computer that SQL Server 2005 is running on uses Windows 2003 or
above OS, yes (so not on Windows 2000 or XP, these use hardcoded policies).
If you are an AD domain member it will use the domain policy, if not it will
use local policy. And what matters is the OS that the SQL Server machine
runs, not the OS that the domain controller runs.

> If AD configured case sensitive. Sql logins will be case sensitive as well
> even sql2002 sort order is 52.

Yes. Windows passwords (and thus SQL passwords) are always case-sensitive in
SQL Server 2005.

> If an application is use ODBC connection to the sql2005, Do I need to
> change the ODBC driver to native ODBC or something?

You should move to the "SQL Native Client" ODBC driver. Although the old
ODBC driver "SQL Server" might actually also support password change
information in the connection string, the protocol doesn't support it before
SQL Native Client .

> Thanks

Reply to this Message