What are the challenges you face when working across database platforms? Take the survey
Options

BUG: Change_Tracking set to ON despite being OFF in the script

Matthew_SontumMatthew_Sontum Posts: 26 Bronze 1
edited May 7, 2018 6:15PM in SQL Compare
I am using SQL Compare 13 and in my database project I have the line:

ALTER TABLE [dbo].[Person] ENABLE CHANGE_TRACKING WITH (TRACK_COLUMNS_UPDATED = OFF);

In the comparison it displays as:

ALTER TABLE [dbo].[Person] ENABLE CHANGE_TRACKING WITH (TRACK_COLUMNS_UPDATED = ON)

And is thus a conflict when compared against the database, where it lists the ALTER statement as:

ALTER TABLE [dbo].[Person] ENABLE CHANGE_TRACKING.

Note: Changing the definition in the script to ALTER TABLE [dbo].[Person] ENABLE CHANGE_TRACKING resolves the issue, but I still consider this a bug, in that explicitly setting it to OFF in the script does not work, and this is how it exists in our source control.
Tagged:

Comments

Sign In or Register to comment.