Options
Constrainst name's tagged as different, but not really
aoflaherty
Posts: 2
How do you work around this issue? SQL Compare wants to drop and recreate several constraints because the names are different, not the content. Is there a way to ignore those differences?
For example each database has a primary key contraint, just with a different name, probably generated from SQL Server:
ALTER TABLE [tableA] ADD CONSTRAINT [PK__tableA__3EE740E8] PRIMARY KEY CLUSTERED ([ColumnA])
verses
ALTER TABLE [tableA] ADD CONSTRAINT [PK__tableA__77F5A112] PRIMARY KEY CLUSTERED ([ColumnA])
In this example, SQL Compare notes it as a difference although I don't consider it one. The program plans to drop and recreate the constraint to synch it up. I would rather not see those kinds of differences in the report or the script.
Suggestions?
Thank you.
Anne
For example each database has a primary key contraint, just with a different name, probably generated from SQL Server:
ALTER TABLE [tableA] ADD CONSTRAINT [PK__tableA__3EE740E8] PRIMARY KEY CLUSTERED ([ColumnA])
verses
ALTER TABLE [tableA] ADD CONSTRAINT [PK__tableA__77F5A112] PRIMARY KEY CLUSTERED ([ColumnA])
In this example, SQL Compare notes it as a difference although I don't consider it one. The program plans to drop and recreate the constraint to synch it up. I would rather not see those kinds of differences in the report or the script.
Suggestions?
Thank you.
Anne
Comments
Simon C