A client of ours has a box dedicated to our application and is happy to change
anything on it to suit our application.

For extremely poor reasons we have an application which tries to create a
dedicated SQL authentication user with a fixed 6 character password. (uses
Upper, lower, number and symbols)

The SQL running on our clients box is SQL2005 and is running on Win Server
2003.

The system is refusing to allow this SQL authenticated user to be created
claiming that the password is not complex enough.

Is there anything we can do to SQL to make it ignore these requirements.

Our client is happy to do this but cannot change the domain policy. Can we
make SQL ignore this policy?

--
Rory

Rorry
Perhaps
CREATE LOGIN [loginame] WITH PASSWORD=N'hjhvdjhjvfhjvfhd',
DEFAULT_DATABASE=[dbname], CHECK_EXPIRATION=OFF, CHECK_POLICY=OFF









"Rory Becker" <rorybecker@newsgroup.nospam> wrote in message
news:3af1034716a068ca9f4bb87cf43d@news.microsoft.c om...
>A client of ours has a box dedicated to our application and is happy to
>change anything on it to suit our application.
>
> For extremely poor reasons we have an application which tries to create a
> dedicated SQL authentication user with a fixed 6 character password. (uses
> Upper, lower, number and symbols)
>
> The SQL running on our clients box is SQL2005 and is running on Win Server
> 2003.
>
> The system is refusing to allow this SQL authenticated user to be created
> claiming that the password is not complex enough.
>
> Is there anything we can do to SQL to make it ignore these requirements.
>
> Our client is happy to do this but cannot change the domain policy. Can we
> make SQL ignore this policy?
>
> --
> Rory
>
>

If you don't want to apply the windows rule for your SQL Server logins, then you can specify this in
the CREATE LOGIN command. For example:

CREATE LOGIN [myLogin]
WITH PASSWORD=N'pwd',
CHECK_EXPIRATION=OFF, CHECK_POLICY=OFF

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi


"Rory Becker" <rorybecker@newsgroup.nospam> wrote in message
news:3af1034716a068ca9f4bb87cf43d@news.microsoft.c om...
>A client of ours has a box dedicated to our application and is happy to change anything on it to
>suit our application.
>
> For extremely poor reasons we have an application which tries to create a dedicated SQL
> authentication user with a fixed 6 character password. (uses Upper, lower, number and symbols)
>
> The SQL running on our clients box is SQL2005 and is running on Win Server 2003.
>
> The system is refusing to allow this SQL authenticated user to be created claiming that the
> password is not complex enough.
>
> Is there anything we can do to SQL to make it ignore these requirements.
>
> Our client is happy to do this but cannot change the domain policy. Can we make SQL ignore this
> policy?
>
> --
> Rory
>
>

Hello Uri,

> Rorry
> Perhaps
> CREATE LOGIN [loginame] WITH PASSWORD=N'hjhvdjhjvfhjvfhd',
> DEFAULT_DATABASE=[dbname], CHECK_EXPIRATION=OFF, CHECK_POLICY=OFF

Thanks Uri and also Tibor...
I will be speaking with the client very soon and will let you know if that
works...


Sounds very promising

Thanks very much

--
Rory

Worked perfectly.

My very grateful thanks to all.

--
Rory