Comments
Sort by recent activity
For all interested, redgate has acknowledged the bug:
We have been able to recreate the behavior that you have seen. I have therefore been able to raise a bug report, reference: SC-5024. / comments
For all interested, redgate has acknowledged the bug:
We have been able to recreate the behavior that you have seen. I have therefore been able to raise a bug report, reference: SC-5024.
I've submitted my issue as a bug.
DB Script:
CREATE DATABASE [CT_DB_TEST];
GO
ALTER DATABASE [CT_DB_TEST] SET CHANGE_TRACKING = ON (CHANGE_RETENTION = 30 DAYS, AUTO_CLEANUP = ON);
GO
USE [CT_DB_TEST];
GO
IF SCHEMA_ID(N'dbo') IS NULL EXECUTE(N'CREATE SCHEMA [dbo]');
GO
CREATE TABLE [dbo].[Table1](
[Id] [int] IDENTITY(1,1) NOT NULL,
[Col1] [int] NOT NULL,
CONSTRAINT [PK_Table1] PRIMARY KEY CLUSTERED
(
[Id] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
) ON [PRIMARY]
GO
ALTER TABLE [dbo].[Table1] ENABLE CHANGE_TRACKING WITH(TRACK_COLUMNS_UPDATED = OFF)
GO
When I use SQL Compare to compare that script to the DB it generates, SQL Compare comes up with this difference:
<line type="different">
<left>ALTER TABLE [dbo].[Table1] ENABLE CHANGE_TRACKING</left>
<right>ALTER TABLE [dbo].[Table1] ENABLE CHANGE_TRACKING WITH (TRACK_COLUMNS_UPDATED = ON)</right>
</line> / comments
I've submitted my issue as a bug.
DB Script:
CREATE DATABASE [CT_DB_TEST];
GO
ALTER DATABASE [CT_DB_TEST] SET CHANGE_TRACKING = ON (CHANGE_RETENTION = 30 DAYS, AUTO_CLEANUP = ON);
GO
USE [CT_DB_TES...