January 19, 2014 at 12:51 pm
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
January 19, 2014 at 10:43 pm
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.
January 20, 2014 at 4:23 pm
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
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply