Re: SQL2005 sp_addsubscription not same as 2000
- From: "Paul Ibison" <Paul.Ibison@xxxxxxxxxxxxx>
- Date: Mon, 4 Dec 2006 15:19:53 -0000
Chris,
if you add a new table to an existing publication using sp_addarticle when
you try to subscribe to that newly added article from an existing
subscription, using sp_addsubscription, the error you mention may be
received. This applies when the existing publication set up with concurrent
snapshot option and means that you can't synchronize subscriptions for such
publications without a complete resynch.
There are 2 unofficial workarounds: (a) you can circumvent the check by
specifying @reserve = 'internal' when you add the subscription for the new
article and the snapshot agent should generate snapshot for the new article
after that and (b) you could change the immediate_sync property in
syspublications to 0 (see sp_changepublication).
Other more official workarounds including changing the sync_method from
'concurrent' to either 'database snapshot' (enterprise edition only) and
'native' (which locks table during snapshot generation). Change the
sync_method will force a reinitialization of all your subscriptions at this
point. Alternatively you could create another publication and use this
instead.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
.
- Prev by Date: Re: SQL2005 sp_addsubscription not same as 2000
- Next by Date: Re: Replication and type conversion
- Previous by thread: Re: SQL2005 sp_addsubscription not same as 2000
- Next by thread: Re: SQL2005 Merge Conflicts Gumming Performance
- Index(es):
Relevant Pages
|
