What is the best way to determine if transactional replication is alive and
well? I would like to know if the snapshots are completed, the articles are
being published, and that replicated transactions are being processed by the
subscriber.
Bob b
run sp_MSenum_snapshot
look for a status of 2, which means complete.
to check that replicated commands are being processed issue the below
select * from distribution.dbo.msdistribution_status
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"bob b" <bobb@.discussions.microsoft.com> wrote in message
news:677477A8-E644-439A-BE90-96B1D94E0B14@.microsoft.com...
> What is the best way to determine if transactional replication is alive
and
> well? I would like to know if the snapshots are completed, the articles
are
> being published, and that replicated transactions are being processed by
the
> subscriber.
> --
> Bob b
Showing posts with label completed. Show all posts
Showing posts with label completed. Show all posts
Wednesday, March 28, 2012
Tuesday, February 21, 2012
replication is completed
We have a server that is replicating information back and forth to 10
different location. My question is how do i know if a location is done
replicating to us. my scenario is that we have 10 stores, each stores as it
makes a sales, the information is replicated back to corporate. Corporate
in turn replicate that information back to the other nine stores. How can i
tell if a store is done downloading information to corporate verse corporate
still trying to push data to the store.
tx in advance.
That depends. Is there ever a point when no transactions are occuring on the
stores? If so you can schedule the agents and after the final job has
completed the central location will have all the data.
Another option is to run sp_browsereplcmds on the publisher and subscriber
until no rows are returned.
You could also query select delivered_transactions from
MSdistribution_history in the distribution database and wait for a value of
delivered_transactions to be 0.
For merge you might want to query select delivery_rate from
MSmerge_history
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"tlee" <tlee@.lang.com> wrote in message
news:OVTyEXXsEHA.904@.TK2MSFTNGP11.phx.gbl...
> We have a server that is replicating information back and forth to 10
> different location. My question is how do i know if a location is done
> replicating to us. my scenario is that we have 10 stores, each stores as
it
> makes a sales, the information is replicated back to corporate. Corporate
> in turn replicate that information back to the other nine stores. How can
i
> tell if a store is done downloading information to corporate verse
corporate
> still trying to push data to the store.
> tx in advance.
>
|||Thanks, i will give it a try.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23C$IATesEHA.3320@.TK2MSFTNGP15.phx.gbl...
> That depends. Is there ever a point when no transactions are occuring on
> the
> stores? If so you can schedule the agents and after the final job has
> completed the central location will have all the data.
> Another option is to run sp_browsereplcmds on the publisher and subscriber
> until no rows are returned.
> You could also query select delivered_transactions from
> MSdistribution_history in the distribution database and wait for a value
> of
> delivered_transactions to be 0.
> For merge you might want to query select delivery_rate from
> MSmerge_history
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "tlee" <tlee@.lang.com> wrote in message
> news:OVTyEXXsEHA.904@.TK2MSFTNGP11.phx.gbl...
> it
> i
> corporate
>
different location. My question is how do i know if a location is done
replicating to us. my scenario is that we have 10 stores, each stores as it
makes a sales, the information is replicated back to corporate. Corporate
in turn replicate that information back to the other nine stores. How can i
tell if a store is done downloading information to corporate verse corporate
still trying to push data to the store.
tx in advance.
That depends. Is there ever a point when no transactions are occuring on the
stores? If so you can schedule the agents and after the final job has
completed the central location will have all the data.
Another option is to run sp_browsereplcmds on the publisher and subscriber
until no rows are returned.
You could also query select delivered_transactions from
MSdistribution_history in the distribution database and wait for a value of
delivered_transactions to be 0.
For merge you might want to query select delivery_rate from
MSmerge_history
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"tlee" <tlee@.lang.com> wrote in message
news:OVTyEXXsEHA.904@.TK2MSFTNGP11.phx.gbl...
> We have a server that is replicating information back and forth to 10
> different location. My question is how do i know if a location is done
> replicating to us. my scenario is that we have 10 stores, each stores as
it
> makes a sales, the information is replicated back to corporate. Corporate
> in turn replicate that information back to the other nine stores. How can
i
> tell if a store is done downloading information to corporate verse
corporate
> still trying to push data to the store.
> tx in advance.
>
|||Thanks, i will give it a try.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23C$IATesEHA.3320@.TK2MSFTNGP15.phx.gbl...
> That depends. Is there ever a point when no transactions are occuring on
> the
> stores? If so you can schedule the agents and after the final job has
> completed the central location will have all the data.
> Another option is to run sp_browsereplcmds on the publisher and subscriber
> until no rows are returned.
> You could also query select delivered_transactions from
> MSdistribution_history in the distribution database and wait for a value
> of
> delivered_transactions to be 0.
> For merge you might want to query select delivery_rate from
> MSmerge_history
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "tlee" <tlee@.lang.com> wrote in message
> news:OVTyEXXsEHA.904@.TK2MSFTNGP11.phx.gbl...
> it
> i
> corporate
>
Labels:
10different,
back,
completed,
database,
forth,
location,
microsoft,
mysql,
oracle,
replicating,
replication,
server,
sql
Subscribe to:
Posts (Atom)