Ok… just found something cool.
SQL 2005 now has password expiration for SQL authentication similar like a domain account.
(NOTE: I am not an expert on this so…..)
I created a user ‘myUser’ so my application could login to the database.
Ran the app only to get a message stating that the account needs to change the password. Hum… never had to do that before.
Anyway, log story short. There are now new security measures in place turned on by default in SQL 2005. When you create a SQL user, you can enforce password policy and even force the user to change their password on next login.
I removed the user and added it back using the below script.
DROP
LOGIN myUser
GO>
CREATE
LOGIN myUser WITH PASSWORD=‘P@ssw0rd’>
, DEFAULT_DATABASE=DefaultDB
, DEFAULT_LANGUAGE=[us_english]
, CHECK_EXPIRATION=OFF –This makes the password never expire
, CHECK_POLICY=OFF –This does not enforce the password policy
GO
EXEC sys.sp_addsrvrolemember @loginame = N‘myUser’, @rolename = N’sysadmin’ (or other role)
GO> 