Solved

SQL server 2005 merge replication procedures

Posted on 2012-04-03
2
179 Views
Last Modified: 2012-04-05
I have a database on an SQL server 2005 named SERVER1 which has approximately 70 tables in a database DB1 that need replicating to another database server SERVER2 which has no database on it yet.
I am considering one of two ways of proceeding to set up a merge replication to the SQL Server 2005 database server SERVER2.

Scenario A:
Set up a SERVER1 as a publisher to publish the 70 tables in DB1
Create a blank database DB1 on SERVER2
Add SERVER2 as a subscriber to SERVER1 publication and proceed with synchronisation.

Scenario B:
Set up a SERVER1 as a publisher to publish the 70 tables in DB1 and create a backup to disk.
Restore the backup to SERVER2 thus creating a DB1 on SERVER2
Remove all replication on SERVER2 DB1
Add SERVER2 as a subscriber to SERVER1 publication and proceed with synchronisation.

I am stating that scenario A is better than scenario B, am I correct, and if so, how can i justify my decision ?
0
Comment
Question by:alcindor
2 Comments
 
LVL 29

Accepted Solution

by:
Paul Jackson earned 500 total points
ID: 37803953
There's not a lot of difference between the two unless there are tables in db1 on server 1 that for some reason you are not replicating in that case scenario b is better as you will get all of the tables not just the ones that are being replicated.

With scenario a if you are replicating all the tables in db1 it will work fine, however if there are some tables that aren't being replicated these will not be created on server 2 when synchronisation happen, so if you need the non-replicated tables on server 2 as well then scenario a is mot the best way to go.

In summary if you let the replication synchronisation process copy over the database schema it will only copy over the tables that are being replicated.
0
 
LVL 75

Expert Comment

by:Anthony Perkins
ID: 37804423
It really depends on the size.  If the database is small go with option A, if not option B.  Notice how I have been particularly vague and that is because I do not know your SLAs
0

Featured Post

Simplifying Server Workload Migrations

This use case outlines the migration challenges that organizations face and how the Acronis AnyData Engine supports physical-to-physical (P2P), physical-to-virtual (P2V), virtual to physical (V2P), and cross-virtual (V2V) migration scenarios to address these challenges.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article will describe one method to parse a delimited string into a table of data.   Why would I do that you ask?  Let's say that you need to pass multiple parameters into a stored procedure to search for.  For our sake, we'll say that we wa…
When writing XML code a very difficult part is when we like to remove all the elements or attributes from the XML that have no data. I would like to share a set of recursive MSSQL stored procedures that I have made to remove those elements from …
Email security requires an ever evolving service that stays up to date with counter-evolving threats. The Email Laundry perform Research and Development to ensure their email security service evolves faster than cyber criminals. We apply our Threat…
With Secure Portal Encryption, the recipient is sent a link to their email address directing them to the email laundry delivery page. From there, the recipient will be required to enter a user name and password to enter the page. Once the recipient …

832 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question