BUG: Change_Tracking set to ON despite being OFF in the script
Matthew_Sontum
Posts: 26 Bronze 1
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 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.
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
Thanks for your post.
This could be something that a support engineer can investigate for you. If you have a support contract could you please send us a ticket for this?
Kind regards
Richard Lynch.
Redgate Software