sql server replication: Hi,

After reading several articles and newsgroups, I still face several doubts
about logshipping procedures.

We have three SQL 2000 servers, one primary (A), one secundary (B) and one
monitoring (C). There is a logshipping configured.

Between A and B there is a WAN.

I need to know how should I proceed in case primary server or WAN line brake
down. In fact, If line is broken, that doesn't mean server A is damage. But,
in this case, I need to change the role of secondary server to be primary. I
know and understand how to do so, but what happens when the line is up again?
I understand there was some transactions that weren't copied before changing
the role of primary and secondary servers.

Does any body could point me in the right way?

Thanks,

Alex - once you've recovered the database on B there's no going back and
there's no posibility of adding the new log from A. After you enter data on
B there is non-convergence on both sides. If you can backup A's current log
before failover and apply it to B then you won't lose anything - can this be
done manually if necessary?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com

Hi Paul,

Thanks a lot for your answer.

So, the best way to put server B into production when there is no line
between A and B, should be to undo the Log Shipping on server A, and on
server B....how could I put database on server B as ready, I mean in
production? Should I run the script that promotes it to primary? I understand
not, as the logshipping is broken.

Thanks a lot,

Alex.

[quoted text, click to view]