As your needs evolve, deployed remote databases may require schema changes. The most common schema changes are adding a new column to an existing table or adding a new table to the database.

Previously, schema changes that affected synchronization required a successful synchronization immediately before making the schema change. This is no longer required. In order to do this, you must use new SQL syntax to store the script version on the synchronization subscription instead of using the ScriptVersion extended option.

The SQL syntax to support this feature is as follows: