Applies ToSQL Server 2016 Service Pack 1 SQL Server 2016 Developer - duplicate (do not use) SQL Server 2016 Enterprise - duplicate (do not use) SQL Server 2016 Enterprise Core - duplicate (do not use) SQL Server 2016 Standard - duplicate (do not use)

Symptoms

When you use Microsoft SQL Server 2016, increased PAGELATCH_EX and PAGELATCH_SH wait time occurs on the database pages that belong to sys.sysobjvalues and sys.sysseobjvalues system tables in TempDB.

Workaround

To work around this issue, review your application and apply the following methods where applicable. Also make sure that you use these methods as best practices in future Transact-SQL development:

  • Remove the DROP TABLE commands for any temporary tables that won't be reused within the same execution of the stored procedure. SQL Server will remove the temporary tables when the session that created the temporary tables has ended.

  • Avoid using the TRUNCATE TABLE command against temporary tables.

  • Avoid altering temporary tables after they have been created.

  • If indexes are created against the temporary table, consider moving these to inline index creation statements within the CREATE TABLE command.

Resolution

This fix is included in the following updates:

Cumulative Update 1 for SQL Server 2016 Service Pack 2

Cumulative Update 9 for SQL Server 2016 Service Pack 1

About SQL Server builds

Each new build for SQL Server contains all the hotfixes and security fixes that were in the previous build. We recommend that you install the latest build for your version of SQL Server:

The latest build for SQL Server 2016

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.