Change Tracking fixes in SQL 2014 SP4 CU4

Share this Post

The Cumulative Update 4 for SQL 2014 SP3 contains these important fixes for Change Tracking technology.

Cumulative Update Package 4 for SQL Server 2014 SP3 – KB4500181
https://www.microsoft.com/en-us/download/details.aspx?id=57663

FIX: Tlog grows quickly when you run auto cleanup procedure in SQL Server 2014, 2016 and 2017
https://support.microsoft.com/en-us/help/4500403/fix-tlog-grows-quickly-when-you-run-auto-cleanup-procedure-in-sql-serv

FIX: Syscommittab cleanup causes a lock escalation that will block the syscommittab flush in SQL Server 2014, 2016 and 2017
https://support.microsoft.com/en-us/help/4512016/fix-syscommittab-cleanup-causes-a-lock-escalation-that-will-block-the

The “fix list” article contains links for installing in cluster and mirroring topology.

Cumulative Update 4 for SQL Server 2014 SP3

https://support.microsoft.com/en-us/help/4500181/cumulative-update-4-for-sql-server-2014-sp3

Always On Availability Groups

In the “rolling upgrade for Always On” an extra step is required to ensure replication components are upgraded on Primary Replica. This is not required when apply the Cumulative update is directly installed on an active SQL Server as CU install will automatically run sp_vupgrade_replication. This is only required as part of rolling-upgrades where “read-only” secondary servers are upgraded prior to failover.

https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/upgrading-always-on-availability-group-replica-instances
Run the following Transact-SQL on the instance that hosts the primary replica:
EXECUTE [master].[sys].[sp_vupgrade_replication];

Chris Skorlinski, SQL Server Escalation Services


Share this Post

About: ReplTalk


Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.