Replication Conundrum

[Gooser]

I have a Replication question that I can't seem to find the problem to.

I have two databases, call them A and B. A is the publisher, B is the subscriber. We have regular transactions going on day to day that need to be replicated from A to B. However, at mid-month, we have to run a batch of updates on database A that really won't become effective on database B until the end of the month.

If I turn off replication, run the batch, then turn replication back on, will the transactions that happened on database A while replication was turned off be replicated to database B? Is there a way to keep that "catch-up" from happening?



v/r

Gooser

Why do today
that which may not need to be done tomorrow --me

The Universal Model

 

[ptheriault]

will the transactions that happened on database A while replication was turned off be replicated to database B?

Yes they will. All transactions are kept in the distribution database so that they can be applied. You can apply filters to your replicated tables that will allow you filter out the data by date.

- Paul
- If at first you don't succeed, find out if the loser gets anything.

 

[mrdenny]

However those filters will keep indivitual rows from being replicated, not transactions.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com