SQL Server Bug: Replication schema change parameter (REPLICATE_DDL) is invalid

Original: SQL Server Bug: Replication schema change parameter (REPLICATE_DDL) is invalid

Recently tested schema change issues for updatable subscriptions, and a bug was found.

In replication, when schema changes are made to the publication database at the publication database, the structure is automatically synchronized to the subscription (this is the replication schema change). For some reason, when you add a field to a table, you do not need to synchronize to the subscription. In the publication properties, there is an option to control that schema changes are not synchronized. Such as:

Only change the value of the copy schema change to false , changing the structure is out of sync, and the change takes effect in real time.

You can also change this parameter by script:

EXEC sp_changepublication @publication = n ' publication ', @property = N ' replicate_ddl ', @value = 0GOEXEC Sp_changepublicat Ion @publication = n ' publication ', @property = N ' replicate_ddl ', @value = 1GO

However, there is a problem with this parameter change in Microsoft SQL Server R2 (RTM) . When the parameter is changed to False , the schema change is not synchronized, but when the parameter is changed back to True , it is found that the structural change is still out of sync. Suspect is a bug, did not find the relevant documentation to explain the problem, and then download Microsoft? SQL Server? Try the R2 Service Pack 3 update. After installing SP3, it's OK! ~ Maybe this feature used less, did not find the problem and fix the document, since SP3 has a fix, that means the official has confirmed the fix.

SQL Server Bug: Replication schema change parameter (REPLICATE_DDL) is invalid