Re: Fault tolerant distributor in merge replication and data mirroring (in SQL Server 2005/2008)


Ok. That's the best option, but it's quite expensive and my customer doesn't
want it. When I said fault-tolerant I didn't mean "real time recovery", I
should better have said that the downtime recovery process should be quite
small: less than two hours.

As it's a Merge Replication there can be this small downtime, that's why I
was saying doing backup/restore of distribution database... but then I don't
know how exactly would connect the subscribers to the distribution or other
issues that can be there and I don't know... or, if as you said, cluster is
the only option.

Thank you!

Josep.

PS: Hilary, sorry for my English :-(



"Hilary Cotter" <hilary.cotter@xxxxxxxxx> escribió en el mensaje
news:uDoLtIiUIHA.5132@xxxxxxxxxxxxxxxxxxxxxxx
Cluster it. It should be a local distributor.


--
http://www.zetainteractive.com - Shift Happens!

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
"Josep" <jmartinez@xxxxxxxx> wrote in message
news:OT0UAqhUIHA.5404@xxxxxxxxxxxxxxxxxxxxxxx
Hello!

My customer has SQL Server 2000 with Merge Replication, implementing a
star tipology: one publisher (also distributor) and 11 push
subscribers.And they want to move to SQL Server 2005/2008 and have a
fault tolerant environment.

I've thought that probably the best is to set up data mirroring for the
publication, but the BOL says that data mirroring is not possible for the
distribution database. So, what's the best way to do implement a fault
tolerant system for the distribution database? (it's not needed to be
automatic)
Maybe doing backups and restores quite ofter of distribution database
from the principal to the mirror?? because we have the point that in
merge replication only changes occurs there when the replication-schema
is changed or a new identity range is given to a subscriber (when using
automatic identity range).


Thanks in advance!

Josep







.

Relevant Pages

  • Re: Replication Cleanup in high volume database
    ... We have one subscriber and are using RAID 10 as recommended. ... before moving to SQL 2005 x64, replication was the weak performance link. ... The distribution database has grown to 9GB in < a week. ... * What other parameters can be changed to keep the transactions only as ...
    (microsoft.public.sqlserver.replication)
  • The subscription(s) have been marked inactive and must be reinitialized.
    ... We have replication set up from our production system to 3 other servers. ... MSrepl_commands table on distribution database was filling up as a result ...
    (microsoft.public.sqlserver.replication)
  • Re: Replication general question
    ... I know it is used in BOL and in a lot of other places. ... refuse to ever implement replication again, because "it doesn't work" or "I ... is on one server, part of the data on another server, and part of the data ... distribution database from server 2 and no agent in the system has the ...
    (microsoft.public.sqlserver.replication)
  • Re: Reinitialization count
    ... You can query the MSsnapshot_history table in the distribution database. ... Looking for a SQL Server replication book? ... download-only publication. ...
    (microsoft.public.sqlserver.replication)
  • Re: General SQL Server 2005 transactional replication question
    ... Looking for a SQL Server replication book? ... presumably all my changes to that database are relayed to ... in the distribution database until it comes back up? ...
    (microsoft.public.sqlserver.replication)
Loading