When you use either a new instance of Microsoft SQL Server 2016 (or 2017) or an instance of SQL Server 2016 (or 2017) that's upgraded from an earlier version of SQL Server, you experience performance issues because of high CPU usage.

Open System Monitor (Perfmon.exe), and then add the ID Thread counter to the Thread performance object for all sqlservr instances. Click View Report to display the information. Note the instance name of the resource monitor based on the thread id that you obtained in step 1.

The Sqlservr.exe file will have a version later than or equal to 10.0:2531.0, but earlier than 10.0:2766.0. If you are using Microsoft SQL Server 2008 RTM or later versions of SQL Server 2008 RTM, the query will return the following version information:

When this occurs, the Sqlservr.exe process sends a message to notify the Fdhost.exe process to process all the existing data in the OSM. While the Fdhost.exe process is processing data, the inbound shared memory (ISM), which is the shared memory from Fdhost.exe to Sqlservr.exe, may become full.

Fixes a problem that may occur when the Check Database Integrity task and the Execute T-SQL Statement task in a maintenance plan may lose database context in certain circumstances in SQL Server 2005 Service Pack 2.

Fixes an issue that occurs when you run DML statements against a table that has partitioned indexes in SQL Server 2008 R2, in SQL Server 2008 or in SQL Server 2012. This issue occurs after the schema of the table is changed, and new partitions are created after the schema changes.

Fixes a poor performance issue that occurs when table-valued functions use many table variables in SQL Server 2008 R2 in SQL Server 2008. When this issue occurs, high contention for the sys.sysmultiobjrefs [2:1:103] table in the Tempdb database occurs.

If the current build of sqlservr.exe is less than the fix build, the advisor generates the alert about this issue. Review the details that are provided in the “Information Collected” section of the advisor alert, and apply the fix that is discussed in this article.

Fixes a backup issue that occurs when you use a backup statement to back up a database in SQL Server 2008, in SQL Server 2008 R2 or in SQL Server 2012 if you enable change tracking on the database. This issue occurs after the database is recovered at least one time.

Download and install SP1 from the download center at Microsoft SQL Server 2014 Service Pack 1 (SP1). Download and install CU4 for SP1 from Cumulative Update 4 for SQL Server 2014 SP1. More Information. How to obtain SQL Server 2014 SP1. SQL Server 2014 SP1 is available for download at the SQL Server 2014 SP1 download page.