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 |
|
booyeeka
Starting Member
10 Posts |
 Posted - 2008-03-21 : 05:11:46
|
| hi all,i did manage to successfully configure log shipping (log shipping works, and changes in primary db are visible on a stanby), but i have problems trying to make standby server as primary.problem is that my database on bouth servers remains read-only (because they are in warm-standby state).i followed MS instructions by using next stored procedures (original primary server is named as winxp, and standby is newyork, shupped database is named nwind):1. on a primary server:USE msdbEXEC sp_change_primary_role 'nwind', @final_state=32. on a standby server:USE msdbEXEC sp_change_secondary_role 'nwind'3. now i have to update moniotr server, and if i use recomended SP, it returns an error 14442:USE msdbEXEC sp_change_monitor_role 'newyork', 'winxp', 'nwind', 'c:\ProductionLogs'... but it works with:USE msdbEXEC sp_change_monitor_role 'newyork', 'nwind', 'winxp', 'c:\ProductionLogs'4. now, databases on a bouth servers are in a warm-standby state, and i don't know how to continue to use them (or to use database on a new primary server).please, if you can help me how to achieve that, i tryed everything, but no luck.thank you in advance! |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-03-21 : 20:21:37
|
| Just run 'restore database db_name with recovery' on secondary server. |
 |
|
|
|
|
|
|
|
log shipping problems