April 24, 2009 at 11:21 am
Hi,
We are upgraded from sql server 2000 to 2005 using in_place upgrade method. Before upgrading, we have some sql logins with blank passwords. After the upgrade, the logins with blank passwods are geeting error saying password is too short.
So my question is does bank passwords allowed in sql server 2005? Do we need to provide password rather than blank?
please advice me
April 24, 2009 at 11:34 am
MS is bringing you kicking and screaming into a more secure password structure. there may be ways around it, but they made it a lot harder to leave systems unsecure.
here's what happens when i try to give an empty string password:
ALTER LOGIN bob WITH PASSWORD = '';
Msg 15118, Level 16, State 1, Line 2
Password validation failed. The password does not meet Windows policy requirements because it is not complex enough.
Lowell
April 24, 2009 at 12:41 pm
When you upgrade a system to SQL Server 2005 and above, the default for logins is to set the CHECK_POLICY property ON and to provide a new password for all SQL accounts.
The CHECK_POLICY property specifies that the Windows password policies on the computer where SQL Server is running will be enforced for this login.
You can turn that option off (not recommended) - and then reset the password to blank.
My recommendation is to keep the policy on, set a reasonably complex password and update your application(s) to use the new password.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply