Log Shipping

I'm fairly certain that this posting should not be in replication, but here goes. I'm not a SQL expert, and I know just enough to keep things running. I'm looking to add some recovery options on top of my current backup to tape rotation for 2 core SQL servers. I setup log shipping and that appears to be working without an issue. I left it in standby mode instead of recovery and I also did a run through on switching the server where the primary db resides. That worked great and on the secondary data was up to date and all looked great.

Now I would like to test this process by taking my primary (test)SQL server down and force the secondary server to have the db available for read/write. Can anyone explain to me the best practies for performing the role change in this scenario?

SQL Server 2000 Enterprise running on Windows 2000 Server

Regards and thanks in advance,

Sean

[922 byte] By [SeanDonnelly] at [2008-1-2]
# 1

To make your secondary be available for read and write, you simply need to recover the secondary database

RESTORE LOG your-db-name WITH RECOVERY

LiZhang at 2007-9-13 > top of Msdn Tech,SQL Server,SQL Server Replication...
# 2

Thank you for the repsonse, I will test out in my dev environment.

Regards,
Sean

SeanDonnelly at 2007-9-13 > top of Msdn Tech,SQL Server,SQL Server Replication...

SQL Server

Site Classified