I have a database with DATA_COMPRESSION=PAGE set on all tables and all indexes, and I generate object scripts to file with RedGate compare 8.0. The generated scripts looks like the one below:
CREATE TABLE [CRDBO].[amortization] ( [id] [int] NOT NULL IDENTITY(10000000, 1), [value_date] [datetime] NOT NULL, [pmnt_date] [datetime] NOT NULL, [pmnt_amount] [numeric] (28, 8) NULL, [pmnt_outstanding] [numeric] (28, 8) NULL, ) ON [PRIMARY] WITH (DATA_COMPRESSION = PAGE) GO ALTER TABLE [CRDBO].[amortization] ADD CONSTRAINT [pk_amo] PRIMARY KEY CLUSTERED ([id]) WITH(DATA_COMPRESSION=PAGE) ON [PRIMARY] GO
A completly valid SQL from what I can see, but Red-Gate Compare generates a parse error when I try to compare my scripts with a database. If I remove the DATA_COMPRESSION=Page option from the script and choose ignore "Data compression" when I compare everything works fine, besides that my data compression will vanish from the target database in the synchronization. Does anyone have another solution? Or does anyone know if Red-Gate are working on a fix? I have reported this as a bug and it is confirmed by Red-Gate, but I haven't seen any fix yet.