July 15, 2009 at 7:58 am
Server A has database X, log ships to Server B.
All is very nice. Except one little thing...
We've encountered a problem similar to restoring a db from A onto B, where the SIDs don't match up between Server A and Server B. (But since the X is Standby/ReadOnly on Server B, we cant just go in and fix them like you can when you restore...)
So users that appear to have permission in the database don't.
I think I know a solution. Drop the logins on Server B, copy the logins from Server A to B, then reset the user - SID relationship with:
EXEC sp_change_users_login 'Update_One', 'Some_User', 'Some_User'
1) I'm not 100% confident that this will work.
2) I'm lazy. Is there any easier approach?
Honor Super Omnia-
Jason Miller
July 15, 2009 at 8:19 am
Yes this is the correct solution. But I think it gives error as the X database on server B is standby. Wait for inputs from others here.......
[font="Verdana"]Thanks
Chandra Mohan[/font]
July 15, 2009 at 11:59 am
If you can drop and re-create the logins on server B then you don't need to synchronize the databases one by one. This is a KB article explaining the login transfer process: http://support.microsoft.com/kb/246133
It'd keep the SIDs identical between A and B - no need to make changes to individual DBs.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply