5

I have two environments: dev and test. Dev has a single SQL instance. Test has three which use merge replication.

When I use Schema Compare between dev and test, every table is always flagged as different because the tables in Test have a few replication artifacts:

  • A generated unique ID for replication: [rowguid] [uniqueidentifier] ROWGUIDCOL NOT NULL CONSTRAINT [MSmerge_df_rowguid_DDDF85B24558D414B8FD278B2219C33A]
  • The primary key marked as NOT FOR REPLICATION (I see there is an option to ignore this in the General tab in Schema Compare Options)
  • CONSTRAINT [repl_identity_range...] that requires the primary key be within the range assigned to that instance

Is there a way to ignore the rowguid column and the repl_identity_range_... constraint when running a schema compare?

TheEsnSiavashi
  • 1,245
  • 1
  • 14
  • 29
Ivy
  • 887
  • 1
  • 7
  • 25
  • SQL Compare from Redgate should have that option: [Ignore NOT FOR REPLICATION](https://documentation.red-gate.com/display/SC12/Setting+project+options) – Lukasz Szozda Jun 27 '17 at 16:46
  • 1
    maybe not what you want but you ought to just add those things to your dev instance - they won't do any harm, and then dev will match test as it should. – gordy Jun 27 '17 at 22:57

1 Answers1

2

Check Ignore not for replication in General tab of Options dialog.

Peter Ivan
  • 1,467
  • 2
  • 14
  • 27