December 7, 2010 at 7:59 am
Replication was working like it was supposed to prior to a rename of the server.
Now after the the rename, the only way replication works is if I manually Reinitialize all Subscriptions.
How do I fix that?
Is there a way to force a replication without a reinitialize? Because when it reinitialize it drops the tables, then creates them but all the grants are gone.
December 7, 2010 at 8:24 pm
If you subscribers already have the all of the data (which they may not since you imply that you have already renamed the server and replication is not operating), you can add subscribers and tell replication that the subscriber already has the data. If you are using the replication sprocs (sp_addsubscriber), the parameter is @sync_type='None'
If you need to deliver a new set of data because the subscriber doesn't have all of the data any more, you probably need to change the definition of the articles in the publication. Replication uses sproc 'sp_addarticle' to add an article to the publication. Parameter @pre_creation_cmd controls what happens when a subscriber already has the table. The articles in your publication are using @pre_creation_cmd = 'DROP'. You probably need to using @pre_creation_cmd ='delete' or @pre_creation_cmd = 'TRUNCATE.
These options are also available from the GUI in Enterprise Manager. Unfortunately, I no longer have a SQL 7 or SQL 2000 instance to check where they are in the GUI.
December 8, 2010 at 6:43 am
HappyCat59,
I just found out about the article properties and it seems to have fixed my replication problem. I want to do a little more testing to verify that it is working.
Thanks for your reply,
Rob
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply