Prev: Moving the Distribution Database to a server with the same name
Next: Failed to replicate row with geomentry column
From: Eddie on 17 Mar 2010 17:11
I have the following senario: SqlServer A in outside the corp firewall in
the DMZ. SqlServer B is inside the corp firewall. I want to sync data from
A to B.

I have set up merge replication and a publisher on B. B is also setup for
Web Syncing. I set up a subscriber to use web sync on A.

I get the following error:
"
Message: The schema script 'xxxxxx.sch' could not be propagated to the
subscriber.
2010-03-17 21:00:31.861 Category:NULL
Source: Microsoft SQL Server Native Client 10.0
Number: 3726
Message: Could not drop object 'dbo.xxxxxxx' because it is referenced by a
FOREIGN KEY constraint.
"

I don't want anything on B to change... only A. Is that possible to do?
From: Paul Ibison on 21 Mar 2010 07:13
The thing is - are the schemas and data already in sync? If so, then you can
set up a nosync initialization. You'll have to be careful if you have
identity columns etc but apart from that it'll be ok. The problem with your
current setup is that the default is to drop the tables at the subscriber
and then recreate. If the data and/or schemas are out of sync, then you'll
need to do a full automatic initialization and have a script which runs as a
pre-snapshot script. This script will drop any foreign keys. A post-snapshot
script will readd them afterwards.
HTH,
Paul Ibison

 | 
Pages: 1
Prev: Moving the Distribution Database to a server with the same name
Next: Failed to replicate row with geomentry column