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.

In Microsoft SQL Server 2008, you see that the CPU usage of the resource monitor is very high when the virtual memory is running low on the server. You can examine the CPU usage of the resource monitor by following these steps:

Fixes an issue in which the Bamalerts.exe and Sqlservr.exe processes consume excessive CPU resources. This issue occurs after you install BizTalk Server 2013 and SQL Server 2012 on a computer to create a BizTalk Server environment.

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.

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:

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.

We recommend that you upgrade your SQL Server installation to the latest SQL Server 2014 service pack. The following update is available from the Microsoft Download Center: Download the latest cumulative update package for SQL Server 2014 SP3 now.

Review and remove any unneeded linked servers from SQL Server (sp_dropserver) to reduce the possibility of any untrusted code being executed within the sqlservr.exe process

In Microsoft SQL Server 2005 Service Pack 2 (SP2), the following tasks in a maintenance plan may lose database context in certain circumstances: For example, if a Check Database Integrity task is configured to check integrity on multiple databases, the task repeatedly checks the default database.

It describes how to obtain the service pack, the list of fixes that are included in the service pack, how to select the correct download based on your currently installed version, and a list of copyright attributions for the product.