all groups > sql server replication > august 2006 >
You're in the

sql server replication

group:

When do we need to delete/recreate a subscription?


When do we need to delete/recreate a subscription? JBs
8/17/2006 11:28:41 AM
sql server replication:

Hello,

I'm using SQL Server for Merge replication and I looking for a list o
actions that require to delete a subsription and to recreate it
Deleting a sub. implies to stop the production and some money loss :(

For example, when modifying a publication table's structure (lik
adding a column) or changing a publication rule (addinng a filter) doe
imply to delete/recreate the sub.? Are there other actions concerned b
the same thing? I walked through many Internet publications an
article, especially on the MS.com website but I couldn't find anythin
anwering my questions :(

In the same way (maybe someone as already done that), is there a way t
automatize subsciptions deletions/recreation attached to a server tha
should be replicated so that downtime time is reduced to its maximum?

Thanks for you help on that topic

--
JB
-----------------------------------------------------------------------
JBs's Profile: http://www.dbtalk.net/m68
View this thread: http://www.dbtalk.net/t32644
Re: When do we need to delete/recreate a subscription? Paul Ibison
8/17/2006 7:18:15 PM
To delete and recreate a subscription is obviously quite a major thing and
done as a last resort. In merge replication, there is no possibility of
dropping the subscription on a per article basis unlike transactional
replication, so for major changes to a table structure you might
reinitialize. Dropping a table from the publication would be the same.
Sometimes people reinitialize as the data is not converged even after the
merge agent runs, but there are other methods of solving this, as it is
usually due to the merge triggers not firing, and dummy updates solve it.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com

Re: When do we need to delete/recreate a subscription? Hilary Cotter
8/19/2006 5:29:13 AM
Certain errors, modification of a publication/article properties, some
schema changes, adding or removing an article. Note that the
force_invalidate_snapshot and force_reinit_subscription switches will tell
you if the change will require a snapshot.

Note that for most errors you will be able to upload changes which occur on
the subscriber before the snapshot is applied which will minimize data loss.

--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.

This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.

Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com



[quoted text, click to view]

AddThis Social Bookmark Button