Fixes a problem in which SQLDUMPER.EXE-initiated dumps take a long time to finish in SQL Server 2017 on Linux.

When you use DBCC STACKDUMP command to generate a SQLDUMPER.EXE initiated dump starting from Cumulative Update 9 (CU 9) for SQL Server 2017 to Cumulative Update 13 (CU 13) for SQL Server 2017, you may notice that it doesn't work.

Symptoms. 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.".

SQL Server 2005 Service Pack 2 is not successfully updated when you try to install or to uninstall a security update. 967095. The Windows Internal Database (WYukon) is removed when you use the Add or Remove Programs item in Control Panel to uninstall a security update for SQL Server 2005.

Resolves a vulnerability that exists in Windows common controls that could allow remote code execution if a user visits a website that contains specially crafted content designed to exploit the vulnerability.

This update contains fixes that were released after the release of SQL Server 2012 SP3. Notes. Cumulative updates are now available at the Microsoft Download Center. Only the most recent cumulative update that was released for SQL Server SP3 is available at the Download Center.

This article describes cumulative update package 7 (build number: 11.0.6579.0) for Microsoft SQL Server 2012 Service Pack 3 (SP3). This update contains fixes that were released after the release of SQL Server 2012 SP3.

This article describes Cumulative Update package 4 (CU4) (build number: 12.0.6329.1) for Microsoft SQL Server 2014 Service Pack 3 (SP3). This update contains fixes that were released after the initial release of SQL Server 2014 SP3.

How to obtain Cumulative Update 8 for SQL Server 2005 Service Pack 2. A supported cumulative update package is now available from Microsoft. However, it is intended to correct only the problems that are described in this article. Apply it only to systems that are experiencing these specific problems.

Resolves a vulnerability in Microsoft SQL Server on systems that are running SQL Server Reporting Services (SSRS).