Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Problems setting up new subscriber for merge replication


Problems setting up new subscriber for merge replication

Author
Message
doh73
doh73
SSC Rookie
SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)

Group: General Forum Members
Points: 32 Visits: 154
Hello,

I would like to know the most common way for setting up new subscribers for merge replication. Is it possible to "fill" an empty database on the new subscriber via initializing it with a new snapshot?

I'm having a hard time initializing a new pull-subscription for an existing merge-subscription (2nd Laptop). I always get errors regarding dependent objects. For example a missing table for a view. I understand that SQL-Server should detect these obvious dependencies und create the objects in the appropriate order (what it actually does with an existing subscriber). But it seems to me that's not the case with the new subscriber.

I tried syncing with/without initialization, empty database, restore of publisher-db (without replication-settings), etc. - no luck.

Is simple initializing the Subscriber with an new Snapshot not sufficient? What else has to be done to add a new subscriber?

Many thanks.

Regards
Ralf
Michael Oberhardt
Michael Oberhardt
Grasshopper
Grasshopper (21 reputation)Grasshopper (21 reputation)Grasshopper (21 reputation)Grasshopper (21 reputation)Grasshopper (21 reputation)Grasshopper (21 reputation)Grasshopper (21 reputation)Grasshopper (21 reputation)

Group: General Forum Members
Points: 21 Visits: 93
Firstly, make sure the snapshot is up to date on the Publisher. You can right click the publication, view snapshot agent status, and run it from there.

As far as the subscriber goes, the issue is you are trying to run it without initialization. That is telling SQL that the database already exists on the subscriber, and contains the full schema and data. You can only use that option if the database exists already, schema AND data. If it doesn't, choose initialize.
phil.doensen
phil.doensen
Grasshopper
Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)

Group: General Forum Members
Points: 20 Visits: 173
SQL Server tries to determine the order of the articles, but if it is not working, you may need to set the
@processing_order yourself

http://msdn.microsoft.com/en-us/library/ms147310(v=sql.90).aspx
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search