sql server replication: Transactional SQL Restore question -- sql server replication

Re: Transactional SQL Restore question

burt_king
1/30/2007 5:08:00 PM

So help me understand why this works. I had thought that since the
transaction log is used to hold the replicated information being pushed to
the subscribers, anything other than a very fast recovery on the subscribers
would require a full restore from the publisher. It sounds like this is
wrong.

[quoted text, click to view]

[quoted text, click to view]

Re: Transactional SQL Restore question

Paul Ibison
1/30/2007 9:00:01 PM

Try to restore from the subscriber backup. Provided the retention period
hasn't been exceeded and you have anonymous subscribers, then you won't lose
any transactions. Otherwise, you could restore from the publisher and do a
nosync initialization as you are on SQL 2000 or just initialize as per
normal.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .

Re: Transactional SQL Restore question

Paul Ibison
1/31/2007 10:48:53 AM

The subscriber holds a copy of the xact number - the last transaction read
from the log and applied to the subscriber. Restoring an older backup on the
subscriber will effectively make the xact number go back in time. However,
perhaps the xact number no longer exists in the MSrepl_commands table and
then we have a problem. So, how long are these transactions kept in the
distribution database? As long as the retention perios for anonymous
subscribers, or if not anonymous enabled, then until all subscribers have
read them or the retention period is reached - the lesser of these 2 times.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages in the sql server replication group.