KB3216543 - FIX: Workloads that utilize many frequent, short transactions in SQL Server 2016 and 2017 may consume more CPU than in SQL Server 2014

Symptoms

New auditing requirements for Common Criteria Compliance (CCC) may cause more CPU consumption in SQL Server 2016 and 2017. This can be more noticeable for workloads utilizing many frequent, short transactions, such as those that involve tempdb. This behavior is occurring even when CCC is not enabled.

Consider the following scenarios:

  • You have a highly transactional workload with a large number of Insert/Update transactions.

  • Your application performs frequent small transactions.

  • Your application relies heavily on tempdb, such as when the application uses INSERT INTO temp table consecutively in many separate transactions.

Resolution

This issue is fixed in the following cumulative updates for SQL Server:

Note:

  • To enable the fix Trace Flag (TF) 3427 must be enabled only from Cumulative Update 2 for SQL Server 2016 SP1 to Cumulative Update 2 for SQL Server 2016 SP2.

  • Starting from Cumulative Update 3 for SQL Server 2016 SP2 and for SQL Server 2017, the Common Criteria Compliance (CCC) must be disabled to enable the fix.

 Cumulative Update 4 for SQL Server 2017

 Cumulative Update 3 for SQL Server 2016 SP2

 Cumulative Update 2 for SQL Server 2016 SP1

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 2017

Latest cumulative update for SQL Server 2016

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References

Learn about the terminologythat Microsoft uses to describe software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×