Advertisement

05.04.2007 at 10:31AM PDT, ID: 22553375
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

9.8

SQL Server Replication - Merge Replication and Transactional Publication with updatable Subscriptions

Asked by purplesoup in MS SQL Server

Tags: , , , ,

SQL Server 2005, replicating two identical SQL Server databases.

I’m having a look at SQL Server replication to see if it is possible to replicate an internal database. I have had a look at merge replication but it is difficult because it adds the GUID columns to all the tables and this causes problems with a number of the stored procedures, therefore I am looking at transactional publication with updatable subscriptions – and am interested in hearing from anyone with experience of this.

I have been reading about it and it appears technically it can support peer-to-peer replication, where changes are updated on both databases and not cycled endlessly, however the main problem with it is there is no mechanism for data conflicts, and one change could potentially just overwrite another with no warning given.

What I am wondering is, do I persevere with the merge replication or it is worth spending time investigating transactional replication with updatable subscriptions as another option, given the constraint above?
Start Free Trial
[+][-]05.04.2007 at 11:56AM PDT, ID: 19033187

View this solution now by starting your 7-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zone: MS SQL Server
Tags: replication, merge, transactional, sql, updatable
Sign Up Now!
Solution Provided By: rboyd56
Participating Experts: 1
Solution Grade: A
 
 
 
Loading Advertisement...
20081112-EE-VQP-42