Symptoms
Assume that you use transactional replication in Microsoft SQL Server 2012 or SQL Server 2014, and you enable updatable subscriptions for this replication. The replication is configured to have lots of articles and publications. After you apply a SQL Server hotfix or security update, the instance on the publisher is in script upgrade mode for a long time.
Cause
The issue occurs because, during the upgrade process, recreating store procedures costs most of the time that can be optimized.
Resolution
The issue was first fixed in the following cumulative update of SQL Server.
Cumulative Update 1 for SQL Server 2014 SP1 /en-us/help/3067839
Cumulative Update 6 for SQL Server 2014 /en-us/help/3031047
Cumulative Update 4 for SQL Server 2012 SP2 /en-us/help/3007556
Cumulative Update 13 for SQL Server 2012 SP1 /en-us/help/3002044
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:
- Latest cumulative update for SQL Server 2014 SP1
- Latest cumulative update for SQL Server 2014
- Latest cumulative update for SQL Server 2012 SP2
- Latest cumulative update for SQL Server 2012 SP1
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.