Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase

Merge replication always fails. Expand / Collapse
Posted Thursday, October 4, 2012 6:57 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, March 2, 2016 7:40 AM
Points: 1, Visits: 64
Asked by: migav


I have a merge replication between 2 sql servers 2005 sp3 that goes up and down.

I get the following error messages:

The schema script 'if object_id(N'[dbo].[Companies]') is not null exec('ALTER TABLE [dbo].[Companies] ADD CONSTRAINT DF_Companies_uuES DEFAULT (0) FOR uuES ')' could not be propagated to the subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001) Get help: http://help/MSSQL_REPL-2147201001

Column already has a DEFAULT bound to it. (Source: MSSQLServer, Error number: 1781) Get help: http://help/1781 Could not create constraint.

See previous errors. (Source: MSSQLServer, Error number: 1750) Get help: http://help/1750

Attached the tables structure.

I took the following actions :

1- On subscriber I backuped the contraints with create to the clipboard.

2- On subscriber I deleted the contraints.

3- On publisher I re-initialized the subscription with create a new snapshot.

I can observe :

- Only 1 constraint propagate to the subscriber - the uuES the same on error message.

- I get the same error message afer the snapshot has finished.

- The sincronization is flapping, goes up and down.


  Post Attachments 
LANDr-publisher.txt (3 views, 36.45 KB)
LANDr-subscriber.txt (2 views, 36.52 KB)
Post #1368368
Posted Tuesday, October 23, 2012 3:29 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, September 3, 2015 3:33 AM
Points: 227, Visits: 675
It looks like you are attempting to add the constraint each time that the synchronisation runs. As it already exists, the script returns a failure result. You should check for the existence of the constraint in your schema script.
Post #1375930
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse