SP_Change_Users_Login

You will have to do that per database.

Check policy can ve turned of using:

Jens K. Suessmeyer

http://www.sqlserver2005.de

JensK.Suessmeyer at 2007-10-2 >

If I understand the problem, you have the same user (i.e. the SID is the same) on all databases, correct? You can find the SID using the following query:

SELECT sid FROM sys.database_principals WHERE name = 'user_name'

And then create a login with the corresponding SID and the password policy setting you need, for example:

CREATE LOGIN [login_name]

WITH PASSWORD = 'password',

CHECK_POLICY = OFF,

SID = 0x<SID_IN_BINARY_FORMAT>

Because the users are mapped to logins via the SID, all database users that are mapped to the same login will be fixed.

Please let us know if this information helped or if you have any additional questions.

Thanks,

-Raul Garcia

SDE/T

SQL Server Engine

RaulGarcia-MS at 2007-10-2 >

It's hard to say without knowing what the purpose of these users is. It also looks like you've had this situation before the upgrade. If you just want to make all users map to the same login, you can create the login, like Raul indicated, and then you can map the users that have a different SID to this same login by using the ALTER USER ... WITH LOGIN statement that I discussed at http://blogs.msdn.com/lcris/archive/2007/02/19/sql-server-2005-some-new-security-features-in-sp2.aspx. This should make all users have that login's sid. But you should understand how you got in this situation in the first place - were these users supposed to really map to the same login? From some background on how logins map to users, it may also help to take a look at this: http://blogs.msdn.com/lcris/archive/2007/03/23/basic-sql-server-security-concepts-logins-users-and-principals.aspx.

Thanks

Laurentiu

LaurentiuCristofor at 2007-10-2 >