Thursday, June 17, 2010

Globally disable CHECK_POLICY in SQL Server

3rd party vendor application Install’s may fail with
“Password validation failed. The password does not meet Windows policy requirements because it is too short” when connecting to SQL server to create database users.



Since most of the SQL commands to create the Database/users are embedded within the vendor install program and the CHECK_POLICY cannot be disabled globally in SQL server, you will have to do it at the login-level only that means when a single CREATE LOGIN statement is used, as you cannot use that in a transaction.

Workaround: add a Trace Flag –T4606 to the SQL server (into the appropriate instance) registry and restart the SQL server.

Using regedit, locate appropriate SQL instance where your Vendor application is going to connect.



Add a new registry key ‘SQLArg3’ with a value –T4606






Restart the SQL server




After running the 3rd party install program, remove the trace flag and restart the SQL server service again.

Last modified : 17th June 2010

No comments:

Post a Comment