Re: Error 3726

From: "Paul Ibison" <Paul.Ibison@xxxxxxxxxxxxx>
Date: Wed, 8 Nov 2006 16:46:10 -0000

I answered this in your other post, but I believe Tom's case was different -
certainly the description is distinct in that he mentions he removed the FK
constraints. It might be that he removed them on the publisher! In this case
he does has the same issue and will need to drop them on the subscriber
before the table is dropped eg via a pre-snapshot script.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .

.

Prev by Date: Re: schema script not propagated - could not drop -forgeign key constr
Next by Date: Re: Sync shema independently of data????
Previous by thread: Re: schema script not propagated - could not drop -forgeign key constr
Next by thread: Re: ReIndexing while using replication Important
Index(es):
- Date
- Thread

Relevant Pages

Re: Replication
... Paul Ibison SQL Server MVP, ... Prev by Date: ...
(microsoft.public.sqlserver.replication)
Re: DTS and replication triggers
... you'll need to deselect the 'use fast load' checkbox. ... Paul Ibison SQL Server MVP, ...
(microsoft.public.sqlserver.replication)
Re: Transactional replication with immediate updating subscribers
... On the first screen of the wizard there is an option to show advanced ... Paul Ibison SQL Server MVP, ...
(microsoft.public.sqlserver.replication)
Re: Best replication strategy
... wizards). ... Paul Ibison SQL Server MVP, ...
(microsoft.public.sqlserver.replication)
Re: schema script not propagated - could not drop -forgeign key constr
... you can use a pre-snapshot script to remove these FKs and then add them back ... Paul Ibison SQL Server MVP, ...
(microsoft.public.sqlserver.replication)