Re: Notifcation of when data replicates - Transactional replication
- From: "Paul Ibison" <Paul.Ibison@xxxxxxxxxxxxx>
- Date: Wed, 21 Dec 2005 16:08:36 -0000
Matthew,
the order of changes is indeed maintained in transactional replication,
provided the articles are in the same publication. If they were in separate
publications with independant agents, the order would depend on the order of
running the agents.
The trigger method could be used to flag the data arriving, and notification
Services or some sort of polling mechanism can be used to check for the
flag's existence. You could also check the distribution history tables to
determine when data was last sent over, but in your case it is the final
flag that seems to really indicate the next process can begin on the
subscriber.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
.
- Follow-Ups:
- References:
- Prev by Date: Re: Replication accross Domains?
- Next by Date: Re: Replication accross Domains?
- Previous by thread: Notifcation of when data replicates - Transactional replication
- Next by thread: Re: Notifcation of when data replicates - Transactional replication
- Index(es):
Relevant Pages
|