Thanks for the reply Dan. I guess you're telling me No. Shame.
The third party application is supposed to handle this automatically to
allow non-technical users to be insulated from SQL Server. Works fine on a
SQL Installation where the password complexity policy is not enabled, but it
was developed for SQL 2000 and they haven't rewritten it yet to allow for it.
As I mentioned, I scripted the creation of 20 of them yesterday, in exactly
the way you've described.
Anyway, I appreciate the feedback!
"Dan Guzman" wrote:
> > My research indicated that it is set in Group Policy, but I haven't found
> > a
> > way to disable it for SQL Server without also disabling it for Users and
> > Computers....
>
> SQL Server will honor the OS complexity requirements unless you override
> this on the CREATE LOGIN. For example:
>
> CREATE LOGIN AppLogin
> WITH
> PASSWORD = 'not complex enough',
> CHECK_POLICY = OFF;
>
>
> --
> Hope this helps.
>
> Dan Guzman
> SQL Server MVP
> http://weblogs.sqlteam.com/dang/
>
> "MangroveMtn" wrote in message
>
> > We sell a third party application that uses SQL 2005 as a back end. It
> > has
> > internal user accounts and creates a matching SQL Login when a user
> > account
> > is created. The default password is not complex and when password
> > complexity
> > testing is enabled on the SQL Server, it causes the process to fail.
> >
> > I'm looking for a way to disable password policy checking just on the SQL
> > Server.
> >
> > My research indicated that it is set in Group Policy, but I haven't found
> > a
> > way to disable it for SQL Server without also disabling it for Users and
> > Computers....
> >
> > Any thoughts?
> >
> > In advance let me say that I understand that it may not be good from a
> > security point of view, and I know that I can script the creation of the
> > matching SQL Logins (I had to do 20 today) with or without security policy
> > enabled.
> >
> > Thanks,
>
> >> Stay informed about: Password complexity 
FAQ
Search
Profile
Private Messages
Log in
