Re: Drop replication question
- From: "Hilary Cotter" <hilary.cotter@xxxxxxxxx>
- Date: Mon, 17 Dec 2007 23:14:15 -0500
Many schema changes will be automatically replicated is the replicate_ddl
parameter is set to true for sp_addpublication and sp_addmergepublication.
There are some which you will have to do the drop subscriptions and drop
publications, for example changes to pk, adding defaults, identities, etc.
The problem with your approach is that there is add overhead and your
subscriber tables have to be recreated each time.
--
http://www.zetainteractive.com - Shift Happens!
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
"Ron" <Ron@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A7ED2B66-F49D-4FD3-AD22-54CD8A54DAB9@xxxxxxxxxxxxxxxx
Using SQL2005 SP2 transactional replication. Whenever we have a deploy to
production that contains DDL, I drop the publication and then drop the
subscription on the replicated server. Once the update is complete, I
recreate the publication with any changes that are necessary and then
re-create the subscription, and then the snapshot agent runs. Is that
what
most people do?
This works fine, but I feel it is overkill. Is there a simpler way to
temporarily disable the replication until the DDL changes are made without
dropping and recreating the publication and subscription?
Is there any negative impact by my dropping and recreating the publication
and subscription.
Thanks
Ron
.
- Follow-Ups:
- Re: Drop replication question
- From: Ron
- Re: Drop replication question
- Prev by Date: Re: mssql 2005 merge snapshot problem
- Next by Date: Re: Merge Replication w/ Web Synchronization Across Non-Trusted Domain
- Previous by thread: Merge Replication w/ Web Synchronization Across Non-Trusted Domain
- Next by thread: Re: Drop replication question
- Index(es):
Relevant Pages
|
