May 19, 2011 at 3:43 am
Hello everyone,
I am curious to know how this would work. I currently do not have the facilities required to try this myself.
Lets say you have two servers running SQL (2005, 2008 doesnt really matter), Server 1 has Database A and Server 2 has Database B. A SQL login for an individual exists on both servers to access those server databases, the Login was created at different times.
You build a new server (Server 3) and use the regular SP's to move the SQL logins from Server 1 to new Server 3, then move database A from server 1 to server 3, you fix the orphaned users and it all works great.
You then move Database B from Server 2 to new Server 3, I guess the SQL login would have a different SID for Database B as this database was accessed by a SQL login on a different server. Would I have to remove the users from Database B and add them back, or would running the SP to fix orphaned users be enough to access Database B on the new server successfully?
Sorry for the long post, but thought someone may have done this already and know the score.
Thanks for reading,
Regards, D.
May 19, 2011 at 6:03 am
I believe the proc that fixes logins no longer works in sql 2008 - I usually script users in this situation as it's easier, especially with schemas unless you don't mind all your users having their own schemas too.
I'm sure there's a post about this elsewhere, in last couple of days.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
May 19, 2011 at 10:44 am
SP_CHANGE_USERS_LOGIN still works in SQL 2008, but it won't in future versions. BOL recommends using ALTER USER instead.
Greg
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply