Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
dholland
Starting Member
11 Posts |
 Posted - 2008-04-29 : 14:38:06
|
| Good afternoon... I have a quick question for you all.I have a primary DB that is log shipping to another DB that is in read-only/standby. I would like to run reports against the machine that is in read-only/standby unfortunately I screwed up when initially restoring the DB's and the users are not properly linked to the database... I just need to be able to run a fixuser for the two users however this can't be done while they are in read only. Last night I took one of the DB's out of read only, ran the fix user script, then took a backup of its self - restored it to put it back into read only and verified logshipping picked back up...Now my question is - is there a way to take the DB out of read only, run the fix user script, and put it right back into read only without having to do a restore from backup to get it back into that state?SQL 2005 Standard |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-04-29 : 22:26:14
|
| No, can't apply log backup once the db is in read/write status. |
 |
|
|
dholland
Starting Member
11 Posts |
Posted - 2008-04-30 : 14:21:14
|
| I solved my own issue... the issue was not that the users were not created.. or that they were not properly linked - the problem was they were the wrong SID's... I needed to get an exact copy of the users from the production box.. just in case anyone needs to do so:http://support.microsoft.com/kb/918992/ |
|
|
|
|
|
|
Standby\Read-Only question