July 16, 2008 at 12:49 pm
Those are called ophaned users because they're not connected to any logins. You can use sp_change_users_login to report on ophaned users and connect them with the proper logins.
Greg
July 17, 2008 at 1:49 am
The sp_change_users_login is used to correct users when there is no login. In this case I have a login but no user. Is there a similar procedure I can use to fix this?
July 17, 2008 at 4:48 am
There is a script to migrate the logins from the old server to the new server.
http://support.microsoft.com/default.aspx?scid=kb;en-us;246133
You need to bring over the logins info including SID's which are part of the login record.
July 17, 2008 at 9:58 am
karen.rogers (7/17/2008)
The sp_change_users_login is used to correct users when there is no login. In this case I have a login but no user. Is there a similar procedure I can use to fix this?
So, you want to replace the users in the restored database with different users linked to existing logins? I think you'll just have to drop the old users and create the new ones. There's no system stored procedure to do that.
Greg
July 18, 2008 at 8:25 am
I have got around my original problem by adding the user to the database that I am restoring from. Thanks to all the replies.
I now have another problem where the authority for one of my database users is being removed from the Login authorities following the restore. The login still exists. Is there a procedure that I can use, similar to the sp_change_users_login, that I can store and run from the master database, passing in the name of the database for which I want to add the authority?
Viewing 5 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply