"CLM" <CLM@discussions.microsoft.com> wrote in message
news:F6ADA485-8F2D-48FE-9346-79E8D4BA8208@microsoft.com...
> I'm about to implement transactional replication from 2000 to 2000 for a
> "failover" type of situation. That is, if we lose the publishing server,
> we
> can pretty easily point various apps, etc. to the subscribing server. But
> that leads to a couple of questions if such an event actually occurs
> (where
> the publisher goes down for an extended outage):
>
> 1. Now I want to repoint to the subscribing server. I look at my
> Replication Monitor and all looks well - everything is bright green. But
> how
> do I really know the tables are synced if this has been running for two
> months uninterrupted? I know Informix has a tool that will compare
> pubisher
> and subscriber - does Sql Server have something like this? What is the
> standard way of handling this situation?
> 2. If the publisher does go down (and I have access to Enterprise
> Manager,
> etc.) and now I'm point the apps to the subscribing server and the app is
> making changes there - then is there some "slick" way to resync in the
> reverse direction? (Besides putting replication on the subscribing server
> instead or just doing a DTS, etc.) Again, I can think of several ways to
> do
> this (after shutting down the apps) but just wanted to see if there was a
> clever way to do this most easily and accurately?
>
> Thx.

"Hilary Cotter" wrote:

> 1) Run a validation. This will confirm everything is the same.
> 2) No, what you have to do is use merge replication which will automagically
> do what you want, or use bi-directional transactional replication and have
> different identity seeds on either side, i.e. odd numbers on the publisher
> and even on the subscriber and use an increment of 2.
>
> --
> 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
>
> "CLM" <CLM@discussions.microsoft.com> wrote in message
> news:F6ADA485-8F2D-48FE-9346-79E8D4BA8208@microsoft.com...
> > I'm about to implement transactional replication from 2000 to 2000 for a
> > "failover" type of situation. That is, if we lose the publishing server,
> > we
> > can pretty easily point various apps, etc. to the subscribing server. But
> > that leads to a couple of questions if such an event actually occurs
> > (where
> > the publisher goes down for an extended outage):
> >
> > 1. Now I want to repoint to the subscribing server. I look at my
> > Replication Monitor and all looks well - everything is bright green. But
> > how
> > do I really know the tables are synced if this has been running for two
> > months uninterrupted? I know Informix has a tool that will compare
> > pubisher
> > and subscriber - does Sql Server have something like this? What is the
> > standard way of handling this situation?
> > 2. If the publisher does go down (and I have access to Enterprise
> > Manager,
> > etc.) and now I'm point the apps to the subscribing server and the app is
> > making changes there - then is there some "slick" way to resync in the
> > reverse direction? (Besides putting replication on the subscribing server
> > instead or just doing a DTS, etc.) Again, I can think of several ways to
> > do
> > this (after shutting down the apps) but just wanted to see if there was a
> > clever way to do this most easily and accurately?
> >
> > Thx.
>
>