Merge replication always fails.

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2005 » SS2K5 Replication » Merge replication always fails.

Merge replication always fails.

Rate Topic

Display Mode

Topic Options

Author

Message

miguel_gavinhos

Posted Thursday, October 04, 2012 6:57 AM

Forum Newbie

Group: General Forum Members
Last Login: Wednesday, October 10, 2012 7:19 AM
Points: 1, Visits: 61

Asked by: migav

Hi!

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.

Migav.

Post Attachments

LANDr-publisher.txt (1 view, 36.45 KB)

LANDr-subscriber.txt (1 view, 36.52 KB)

Post #1368368

irobertson

Posted Tuesday, October 23, 2012 3:29 AM

SSC Veteran

Group: General Forum Members
Last Login: Yesterday @ 3:39 AM
Points: 210, Visits: 574

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 »

Permissions