Re: General SQL Server 2005 transactional replication question

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hilary,

In addition to my earlier reply to your reply:
Does bidirectional replication necessarily involve a lot of scripting - ie:
enabling each article for replication in each database? Or is there a short
cut via wizards or higher level constructs?
Is it possible to add additional read-only subscriptions?

Thanks,
Kev.

"Hilary Cotter" wrote:

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: Errors in Directory Service Event Viewer
    ... >condition persists then please restore the database from a previous backup. ... >following directory partition. ... >Sites and Services for the KCC to create a spanning tree replication ... >- Add a Connection object to a domain controller that contains the directory ...
    (microsoft.public.windows.server.active_directory)
  • Errors in Directory Service Event Viewer
    ... Event Category: Database Page Cache ... following directory partition. ... Sites and Services for the KCC to create a spanning tree replication ... - Add a Connection object to a domain controller that contains the directory ...
    (microsoft.public.windows.server.active_directory)
  • Reinitializing Subscriptions
    ... I am new to SQL Server Replication so I still have a cloud over my ... I have the Northwind database setup on Windows 2000 ... Reinitializing Subscriptions. ... the laptops will trickle in over time ...
    (microsoft.public.sqlserver.replication)
  • Re: Replication/Sychronization and security
    ... When put on the network it takes several seconds for those close to ... I am told that our network drives are for data storage (word/excel ... explore the possiblity of replication as a solution. ... >> database to decrease the potential for breach. ...
    (microsoft.public.access.replication)
  • Re: Need help determining where the problem is in my AD replicas
    ... I would demote and promote Education make sure you get a full backup though. ... > Event Source: NTDS Replication ... > changes received from the following source domain controller. ... > 8451 The replication operation encountered a database error. ...
    (microsoft.public.windows.server.active_directory)