Merge pull request #8339 from MicrosoftDocs/main

aartig13 · web-flow · commit 039367d68822 · 2025-02-27T13:54:12.000-06:00
SQL Server 2019 CU 32 release history - merge main to live
diff --git a/support/azure/synapse-analytics/dedicated-sql/query-execution-performance/dsql-perf-common-query-errors.md b/support/azure/synapse-analytics/dedicated-sql/query-execution-performance/dsql-perf-common-query-errors.md
@@ -57,4 +57,4 @@ Use the following guidance to troubleshoot common failures, errors, and exceptio
 
 - Query the DMV [sys.dm_pdw_errors](/sql/relational-databases/system-dynamic-management-views/sys-dm-pdw-errors-transact-sql) for errors
 - [Troubleshoot dedicated SQL pool (formerly SQL DW) in Azure Synapse Analytics](/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-troubleshoot)
-- [Troubleshoot a slow query on a dedicated SQL pool](/troubleshoot/azure/synapse-analytics/dedicated-sql/query-execution-performance/troubleshoot-dsql-perf-slow-query)
+- [Troubleshoot a slow query on a dedicated SQL pool](troubleshoot-dsql-perf-slow-query.md)
diff --git a/support/azure/virtual-machines/windows/allocation-failure.md b/support/azure/virtual-machines/windows/allocation-failure.md
@@ -82,7 +82,7 @@ To work around this issue, use one of the following methods:
 
 - For a new VM deployment, if it can be part of a different availability set, create the VM in a different availability set (in the same region or zone). This new VM can then be added to the same virtual network.
 
-- Consider resizing the VM to a different size that might have more availability in the region or zone. To ensure that the VM sizes are supported in your availability set, use [availability sets - List Available Sizes - REST API](/troubleshoot/azure/virtual-machines/windows/virtual-machines-availability-set-supportability).
+- Consider resizing the VM to a different size that might have more availability in the region or zone. To ensure that the VM sizes are supported in your availability set, use [availability sets - List Available Sizes - REST API](virtual-machines-availability-set-supportability.md).
 
 - Stop (deallocate) all VMs in the same availability set, and then start all applicable VMs in a batch to allow the allocation from all available clusters, rather than just the cluster where the availability set is currently allocated.
   
@@ -110,7 +110,7 @@ To work around this issue, use one of the following methods:
 
 - Resize the VMs
 
-  Consider resizing the VM to a different size that might have more availability in the region or zone. To ensure that the VM sizes are supported in your Availability Set, use [Availability Sets - List Available Sizes - REST API](/troubleshoot/azure/virtual-machines/windows/virtual-machines-availability-set-supportability).
+  Consider resizing the VM to a different size that might have more availability in the region or zone. To ensure that the VM sizes are supported in your Availability Set, use [Availability Sets - List Available Sizes - REST API](virtual-machines-availability-set-supportability.md).
 
 - Change the region or zone
 
diff --git a/support/sql/releases/linux/release-history-2019.md b/support/sql/releases/linux/release-history-2019.md
@@ -4,7 +4,7 @@ description: This article contains the release history for SQL Server 2019 runni
 author: rwestMSFT
 ms.author: randolphwest
 ms.reviewer: amitkh, vanto
-ms.date: 02/13/2025
+ms.date: 02/27/2025
 appliesto:
   - SQL Server 2019
 ms.custom: sap:Installation, Patching, Upgrade, Uninstall, evergreen, linux-related-content
@@ -21,6 +21,7 @@ The following table lists the release history for [!INCLUDE [sql-server-2019](..
 
 | Release                    | Version       | Release date |
 | -------------------------- | ------------- | ------------ |
+| [CU 32](#CU32)             | 15.0.4430.1   | 2025-02-27   |
 | [CU 31](#CU31)             | 15.0.4420.2   | 2025-02-13   |
 | [CU 30](#CU30)             | 15.0.4415.2   | 2024-12-12   |
 | [CU 29 GDR](#CU29-GDR)     | 15.0.4410.1   | 2024-11-12   |
@@ -64,9 +65,9 @@ The following table lists the release history for [!INCLUDE [sql-server-2019](..
 | [GA](#GA)                  | 15.0.2000.5   | 2019-11-04   |
 | [GDR 1](#GDR1)             | 15.0.2070.41  | 2019-11-04   |
 
-## <a id="CU31"></a> CU 31 (February 2025)
+## <a id="CU32"></a> CU 32 (February 2025)
 
-This is the Cumulative Update 31 (CU 31) release of [!INCLUDE [sql-server-2019](../../includes/versions/sql-server-2019.md)]. The [!INCLUDE [sql-server-database-engine](../../includes/versions/sql-server-database-engine.md)] version for this release is 15.0.4420.2. For information about the fixes and improvements in this release, see the [Support article](/troubleshoot/sql/releases/sqlserver-2019/cumulativeupdate31).
+This is the Cumulative Update 32 (CU 32) release of [!INCLUDE [sql-server-2019](../../includes/versions/sql-server-2019.md)]. The [!INCLUDE [sql-server-database-engine](../../includes/versions/sql-server-database-engine.md)] version for this release is 15.0.4430.1. For information about the fixes and improvements in this release, see the [Support article](/troubleshoot/sql/releases/sqlserver-2019/cumulativeupdate32).
 
 > [!IMPORTANT]  
 > This is the final cumulative update for [!INCLUDE [sql-server-2019](../../includes/versions/sql-server-2019.md)].
@@ -75,6 +76,22 @@ This is the Cumulative Update 31 (CU 31) release of [!INCLUDE [sql-server-2019](
 
 For manual or offline package installations, you can download the RPM and Debian packages with the information in the following table:
 
+| Distribution | Package version | Downloads |
+| --- | --- | --- |
+| **RHEL 8.x RPM packages** | 15.0.4430.1-1 | [Database Engine RPM package](https://packages.microsoft.com/rhel/8/mssql-server-2019/Packages/m/mssql-server-15.0.4430.1-1.x86_64.rpm)<br />[Extensibility RPM package](https://packages.microsoft.com/rhel/8/mssql-server-2019/Packages/m/mssql-server-extensibility-15.0.4430.1-1.x86_64.rpm)<br />[Java Extensibility RPM package](https://packages.microsoft.com/rhel/8/mssql-server-2019/Packages/m/mssql-server-extensibility-java-15.0.4430.1-1.x86_64.rpm)<br />[Full-Text Search RPM package](https://packages.microsoft.com/rhel/8/mssql-server-2019/Packages/m/mssql-server-fts-15.0.4430.1-1.x86_64.rpm)<br />[High Availability RPM package](https://packages.microsoft.com/rhel/8/mssql-server-2019/Packages/m/mssql-server-ha-15.0.4430.1-1.x86_64.rpm)<br />[PolyBase RPM package](https://packages.microsoft.com/rhel/8/mssql-server-2019/Packages/m/mssql-server-polybase-15.0.4430.1-1.x86_64.rpm) |
+| **SLES 15 RPM packages**<br /><br />(Get RPM packages for [SLES 12](https://packages.microsoft.com/sles/12/mssql-server-2019/Packages/m/)) | 15.0.4430.1-1 | [Database Engine RPM package](https://packages.microsoft.com/sles/15/mssql-server-2019/Packages/m/mssql-server-15.0.4430.1-1.x86_64.rpm)<br />[Extensibility RPM package](https://packages.microsoft.com/sles/15/mssql-server-2019/Packages/m/mssql-server-extensibility-15.0.4430.1-1.x86_64.rpm)<br />[Java Extensibility RPM package](https://packages.microsoft.com/sles/15/mssql-server-2019/Packages/m/mssql-server-extensibility-java-15.0.4430.1-1.x86_64.rpm)<br />[Full-Text Search RPM package](https://packages.microsoft.com/sles/15/mssql-server-2019/Packages/m/mssql-server-fts-15.0.4430.1-1.x86_64.rpm)<br />[High Availability RPM package](https://packages.microsoft.com/sles/15/mssql-server-2019/Packages/m/mssql-server-ha-15.0.4430.1-1.x86_64.rpm)<br />[PolyBase RPM package](https://packages.microsoft.com/sles/15/mssql-server-2019/Packages/m/mssql-server-polybase-15.0.4430.1-1.x86_64.rpm) |
+| **Ubuntu 20.04 Debian packages**<br /><br />(Get Debian packages for [Ubuntu 18.04](https://packages.microsoft.com/ubuntu/18.04/mssql-server-2019/pool/main/m/mssql-server/)) | 15.0.4430.1-1 | [Database Engine Debian package](https://packages.microsoft.com/ubuntu/20.04/mssql-server-2019/pool/main/m/mssql-server/mssql-server_15.0.4430.1-1_amd64.deb)<br />[Extensibility Debian package](https://packages.microsoft.com/ubuntu/20.04/mssql-server-2019/pool/main/m/mssql-server-extensibility/mssql-server-extensibility_15.0.4430.1-1_amd64.deb)<br />[Java Extensibility Debian package](https://packages.microsoft.com/ubuntu/20.04/mssql-server-2019/pool/main/m/mssql-server-extensibility-java/mssql-server-extensibility-java_15.0.4430.1-1_amd64.deb)<br />[Full-Text Search Debian package](https://packages.microsoft.com/ubuntu/20.04/mssql-server-2019/pool/main/m/mssql-server-fts/mssql-server-fts_15.0.4430.1-1_amd64.deb)<br />[High Availability Debian package](https://packages.microsoft.com/ubuntu/20.04/mssql-server-2019/pool/main/m/mssql-server-ha/mssql-server-ha_15.0.4430.1-1_amd64.deb)<br />[PolyBase Debian package](https://packages.microsoft.com/ubuntu/20.04/mssql-server-2019/pool/main/m/mssql-server-polybase/mssql-server-polybase_15.0.4430.1-1_amd64.deb) |
+
+Go back to the [release history](#release-history).
+
+## <a id="CU31"></a> CU 31 (February 2025)
+
+This is the Cumulative Update 31 (CU 31) release of [!INCLUDE [sql-server-2019](../../includes/versions/sql-server-2019.md)]. The [!INCLUDE [sql-server-database-engine](../../includes/versions/sql-server-database-engine.md)] version for this release is 15.0.4420.2. For information about the fixes and improvements in this release, see the [Support article](../sqlserver-2019/cumulativeupdate31.md).
+
+### Package details
+
+For manual or offline package installations, you can download the RPM and Debian packages with the information in the following table:
+
 | Distribution | Package version | Downloads |
 | --- | --- | --- |
 | **RHEL 8.x RPM packages** | 15.0.4420.2-2 | [Database Engine RPM package](https://packages.microsoft.com/rhel/8/mssql-server-2019/Packages/m/mssql-server-15.0.4420.2-2.x86_64.rpm)<br />[Extensibility RPM package](https://packages.microsoft.com/rhel/8/mssql-server-2019/Packages/m/mssql-server-extensibility-15.0.4420.2-2.x86_64.rpm)<br />[Java Extensibility RPM package](https://packages.microsoft.com/rhel/8/mssql-server-2019/Packages/m/mssql-server-extensibility-java-15.0.4420.2-2.x86_64.rpm)<br />[Full-Text Search RPM package](https://packages.microsoft.com/rhel/8/mssql-server-2019/Packages/m/mssql-server-fts-15.0.4420.2-2.x86_64.rpm)<br />[High Availability RPM package](https://packages.microsoft.com/rhel/8/mssql-server-2019/Packages/m/mssql-server-ha-15.0.4420.2-2.x86_64.rpm)<br />[PolyBase RPM package](https://packages.microsoft.com/rhel/8/mssql-server-2019/Packages/m/mssql-server-polybase-15.0.4420.2-2.x86_64.rpm) |
diff --git a/support/windows-365/troubleshoot-windows-365-business.md b/support/windows-365/troubleshoot-windows-365-business.md
@@ -38,7 +38,7 @@ If the automatic enrollment of new Cloud PCs into the Microsoft Intune setting i
 
 | Error | Troubleshooting steps |
 | --- | --- |
-| To complete the setup, ask your administrator to update policy settings in Microsoft Intune to enroll this device. | Check the Intune settings you might have previously set on your tenant. For more information, see [Troubleshoot policies and profiles](/troubleshoot/mem/intune/device-configuration/troubleshoot-policies-in-microsoft-intune). Once the issue is fixed, either you or the user can reset the Cloud PC. |
+| To complete the setup, ask your administrator to update policy settings in Microsoft Intune to enroll this device. | Check the Intune settings you might have previously set on your tenant. For more information, see [Troubleshoot policies and profiles](../mem/intune/device-configuration/troubleshoot-policies-in-microsoft-intune.md). Once the issue is fixed, either you or the user can reset the Cloud PC. |
 | To complete the setup, ask your administrator to remove restrictions preventing Intune from allowing Windows enrollment.| You might have set up enrollment restrictions on your Intune tenant. For more information, see [Enrollment restrictions overview](/mem/intune/enrollment/enrollment-restrictions-set). Once the restrictions are removed, either you or the user can reset the Cloud PC. |
 | To complete the setup, ask your administrator to correct the configuration of the Mobile Device Management discovery URL in Intune.| Confirm that the MDM discovery URL is the default for Intune. Follow steps 1-4 to set it in [Configure automatic MDM enrollment](/mem/intune/enrollment/windows-enroll#configure-automatic-mdm-enrollment). Once the MDM discovery URL is set to the default, either you or the user can reset the Cloud PC. |
 
diff --git a/support/windows-365/windows-365-boot-known-issues.md b/support/windows-365/windows-365-boot-known-issues.md
@@ -159,7 +159,7 @@ If you configured your device for Windows 365 Boot using the [Windows 365 Boot G
 2. Search for the device configuration profile that contains "Windows 365 Boot Device Configuration Policy" in its name.
 3. Make sure that the "Cloud Desktop" configuration is configured with the **Windows 365 Boot Mode** setting set to **Enable Windows 365 Boot Desktop**.
 4. Select **Device assignment status** and make sure that the configuration policy was successfully applied to it.
-5. If the check-in status isn't successful, see [Troubleshooting policies and profiles in Microsoft Intune](/troubleshoot/mem/intune/device-configuration/troubleshoot-policies-in-microsoft-intune).
+5. If the check-in status isn't successful, see [Troubleshooting policies and profiles in Microsoft Intune](../mem/intune/device-configuration/troubleshoot-policies-in-microsoft-intune.md).
 
 If the problem persists, reinstall the physical device's operating system as explained in [Windows 365 Boot physical device requirements](/windows-365/enterprise/windows-365-boot-physical-device-requirements).
 
@@ -175,7 +175,7 @@ If you configured your device for Windows 365 Boot using the [Windows 365 Boot G
 2. Search for the device configuration profile that contains "Windows 365 Boot Device Configuration Policy" in its name.
 3. Make sure that the "Windows Logon" configuration is configured with the **Override Shell Program** setting set to **Apply Lightweight shell**.
 4. Select **Device assignment status** and make sure that the configuration policy was successfully applied to it.
-5. If the check-in status isn't successful, see [Troubleshooting policies and profiles in Microsoft Intune](/troubleshoot/mem/intune/device-configuration/troubleshoot-policies-in-microsoft-intune).
+5. If the check-in status isn't successful, see [Troubleshooting policies and profiles in Microsoft Intune](../mem/intune/device-configuration/troubleshoot-policies-in-microsoft-intune.md).
 
 If the problem persists, reinstall the physical device's operating system as explained in [Windows 365 Boot physical device requirements](/windows-365/enterprise/windows-365-boot-physical-device-requirements).
 
