Timeline for How do I fix an Orphaned User in Log Shipped version of a SQL Server 2008 database
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 9, 2015 at 8:43 | comment | added | Sina Hassanpour | if you 1. have the login and password, then you can just use it in the code I mentioned, and instead of all users and the GUID, you just need to make the cursor over you list of username and passwords. 2. don't have the logins and passwords but the are already created server level and you have them on you sql server. then you just need to use exec sp_change_users_login 'Auto_fix' ,@UserName instead in the code and don't use the password. hope it helps. | |
| Dec 8, 2015 at 22:25 | comment | added | Kendor | The development box (secondary) has users/logins that I'm nervous about breaking. Is there any way to do this, where I get the SID of the user that I want to also be on the production (primary) from the secondary system, and then create that user on production (primary) with the SID from the secondary box? I may have really fouled things up as I tried to drop the user on the primary box, but was not able to drop that database reference to that user (something to do with ownership). | |
| Dec 7, 2015 at 9:54 | history | answered | Sina Hassanpour | CC BY-SA 3.0 |