PSSDIAG is a general purpose diagnostic collection utility that Microsoft Product Support Services uses to collect various logs and data files. PSSDIAG can natively collect Performance Monitor logs, SQL Profiler traces, SQL Server blocking script output, Windows Event Logs, and SQLDIAG output.

When the SQLDiag utility runs on SQL Server 2017 or 2019, it may fail to generate output because of missing stored procedure temp.dbo.sp_sqldiag14. Additionally, you may receive the following error messages:

Fixes an issue in which the "Function result: 87. Message: The parameter is incorrect" error occurs. This issue occurs when you run the SQLdiag utility.

Microsoft has released security bulletin MS08-040. To view the complete security bulletin, visit one of the following Microsoft Web sites: The following table lists the known issues with this security update. To use the table, look in the top two rows of the table.

To apply this cumulative update package, you must be running SQL Server 2016 SP1. You may have to restart the computer after you apply this cumulative update package. To use one of the hotfixes in this package, you do not have to make any changes to the registry.

Download the latest cumulative update package for SQL Server 2014 SP3 now. If the download page does not appear, contact Microsoft Customer Service and Support to obtain the cumulative update package.

Download the latest cumulative update package for SQL Server 2014 SP3 now. If the download page does not appear, contact Microsoft Customer Service and Support to obtain the cumulative update package.

Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

Resolves a vulnerability in SQL Server that could allow remote code execution if untrusted users have access to an affected system or if a SQL injection vulnerability exists on an affected system.

When you run a distributed query that uses a linked server in Microsoft SQL Server 2005 or in Microsoft SQL Server 2008, the execution fails. Additionally, you receive the following error message: OLE DB provider "SQLNCLI" for linked server " Linked Server " returned message "No transaction is active.".