Symptoms
Assume that you have configured Transaction replication that has a value of "immediate_sync=false" on a highly transactional database. After you add a new table to the publication, you notice that the distribution agent doesn't apply creation commands that are related to the newly added table on the subscriber.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Resolution
This problem is fixed in the following cumulative updates for SQL Server:
Note To resolve this issue, you need to apply the associated cumulative update to the servers of both the Publisher and Distributor in a replication topology.
About cumulative updates for SQL Server:
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
Workaround
To work around this problem, do the following:
-
To make sure that this issue doesn't occur in future, change the immediate_sync value to true.
-
Stop the log reader agent before you add the article, and then restart the log reader agent after the new snapshot is generated.
-
Stop the distribution agent before you add the article, and then restart the distribution agent after the new snapshot is generated.
References
Learn about the terminology that Microsoft uses to describe software updates.
