Re: General SQL Server 2005 transactional replication question

Tech-Archive recommends: Fix windows errors by optimizing your registry

I would use bi-directional transaction replication with push subscribers.
With the NFR property on your triggers it will work correctly. Peer-to-peer
does offer the feature where you can replicate ddl. With pure bi-directional
replication you will have to drop the publications before making schema
changes.

I would not recommend using queued, it is best used when the majority of the
DML originates on the publisher.

--
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



"Kev" <Kev@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2FDF2BB2-1861-4400-B616-82C0273A9E80@xxxxxxxxxxxxxxxx
I want to implement transactional replication for failover purposes. I need
to replicate data from a primary database to a secondary one that will be
used if the primary goes down. In the event of a primary failure I need to
switch the applications to run off the secondary. When the primary is back
up
I then need to update it with all the changes made to the secondary while
the
primary was down, switch the replication direction, and switch the
applications back to the primary again.

I'd like some advise on how best to set this up. For instance:
1) How do I go about delivering secondary updates back to the repaired
primary?
2) Should I use push or pull subscription?
3) The database uses a number of triggers. How should I ensure that
replication works correctly for these - is it just a matter of using the
NOT
FOR REPLICATION option? I've read a couple of posts indicating that this
may
not work properly in the case of updateable subscriptions.
4)Does peer-to-peer replication offer any advantages over the traditional
publication-subscription in this scenario?

Any assistance much appreciated. Apologies for the scope of the question,
but I'm new to sql server replication and would like some expert advice to
get me started.


.

Relevant Pages

  • Re: Can merge replication be used to keep two database in sync
    ... suggest you follow up with Phil if you have more questions about his remarks ... Looking for a SQL Server replication book? ... You can use the conflict viewer to "rollback" replication changes, ... >> there dozens of subscribers, but over 90% of the changes occured on the ...
    (microsoft.public.sqlserver.replication)
  • Re: Can merge replication be used to keep two database in sync
    ... You can use the conflict viewer to "rollback" replication changes, ... Looking for a SQL Server replication book? ... > there dozens of subscribers, but over 90% of the changes occured on the ...
    (microsoft.public.sqlserver.replication)
  • Re: Can merge replication be used to keep two database in sync
    ... the number of subscribers before it started slowing down. ... If you are going to post numbers, particularly with the replication engine, ... in SQL Server 6.5, I've had implementations in production that have ALWAYS ... Broken down by transaction per minute ...
    (microsoft.public.sqlserver.replication)
  • Re: Merge or Trans with QUS best when publishing partitions of database to slow subscribers
    ... With queued replication the single queue does serve all subscribers. ... No real conflict detection and resolution. ... The majority of the DML should originate on the publisher. ...
    (microsoft.public.sqlserver.replication)
  • Re: Trasactional Replication problems
    ... >should have 13000 lines after a snapshot. ... Enable Replication Agents for Logging to Output Files in SQL ... >all data will be transfer to the subscribers in this transactions? ... which means that all available transactions are ...
    (microsoft.public.sqlserver.replication)