Merge pull request #8127 from simonxjx/simon-5

Updates to SQL 2019 CU KB articles

Author: Simonx Xu

support/sql/releases/sqlserver-2019/cumulativeupdate26.md

@@ -16,7 +16,7 @@ _Version:_   15.0.4365.2
 
 ## Summary
 
-This article describes Cumulative Update package 26 (CU26) for Microsoft SQL Server 2019. This update contains 24 [fixes](#improvements-and-fixes-included-in-this-update) that were issued after the release of SQL Server 2019 Cumulative Update 25, and it updates components in the following builds:
+This article describes Cumulative Update package 26 (CU26) for Microsoft SQL Server 2019. This update contains 23 [fixes](#improvements-and-fixes-included-in-this-update) that were issued after the release of SQL Server 2019 Cumulative Update 25, and it updates components in the following builds:
 
 - SQL Server - Product version: **15.0.4365.2**, file version: **2019.150.4365.2**
 - Analysis Services - Product version: **15.0.35.45**, file version: **2018.150.35.45**
@@ -33,11 +33,11 @@ SQL Server 2019 CU14 introduced a [fix to address wrong results in parallel plan
 
 Microsoft is working on a fix for this issue and it will be available in a future CU.
 
-### Issue two: Error 1204 when applying the fix of Bug 2830668
+### Issue two: Possibility of error 1204 due to disabled lock escalation
 
-SQL Server 2019 CU26 introduced the fix of [Bug 2830668](#2830668) that might disable lock escalation, which causes error 1204 "The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time."
+SQL Server 2019 CU26 introduced a regression that can disable lock escalation, which causes error 1204 "The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time."
 
-To work around this issue, you can uninstall the CU26 or install the next [CU27](cumulativeupdate27.md). Microsoft is working on the original latch time-out issue and the fix will be available in a future CU.
+To work around this issue, you can uninstall the CU26 or install the [CU28](cumulativeupdate28.md).
 
 ## Improvements and fixes included in this update
 
@@ -55,7 +55,6 @@ For more information about the bugs that are fixed and enhancements that are inc
 | <a id=2893029>[2893029](#2893029) </a> | Fixes an issue in which the global primary or forwarder in a distributed availability group can't connect to the listener of the other availability group for a while after the local availability group fails over between replicas in multi-subnet configurations. | SQL Server Engine | High Availability and Disaster Recovery | Windows |
 | <a id=2937599>[2937599](#2937599) </a> | Fixes an issue in which the `sp_server_diagnostics` stored procedure doesn't respond to the Always On availability group (AG) resource DLL within the `HealthCheckTimeout` when the I/O takes a long time, which causes unnecessary restart and failover. For example, when the `sp_server_diagnostics` stored procedure is waiting for the `PREEMPTIVE_OS_GETFINALFILEPATHBYHANDLE` wait type. </br></br>**Note**: To apply this fix, you need to turn on trace flag 16301, which is off by default. Tracing is added for this event regardless of the trace flag.| SQL Server Engine | High Availability and Disaster Recovery | All |
 | <a id=2920065>[2920065](#2920065) </a> | Fixes an issue in which an unreliable network connection causes an unsuccessful status during backup to a network share, which causes the SQL Server instance to stop responding.| SQL Server Engine | Linux | Linux |
-| <a id=2830668>[2830668](#2830668) </a> | Fixes a latch time-out issue that you encounter when fetching the next value for sequence objects, which is due to self-deadlock during lock escalation. | SQL Server Engine | Metadata| All |
 | <a id=2984804>[2984804](#2984804) </a> | Fixes an issue in the lock manager that might cause random access violations and dumps on secondary replicas when the primary replica has 16 or more processors, and the secondary replicas have less than 16 processors.| SQL Server Engine | Metadata| All |
 | <a id=2936214>[2936214](#2936214) </a> </br><a id=2936218>[2936218](#2936218) </a> </br><a id=2941530>[2941530](#2941530) </a> </br><a id=2950263>[2950263](#2950263) </a> | [FIX: Scalar UDF Inlining issues in SQL Server 2022 and 2019 (KB4538581)](https://support.microsoft.com/help/4538581)| SQL Server Engine | Programmability | All |
 | <a id=2950261>[2950261](#2950261) </a> | Fixes the following SQL Server assertion failure: </br></br>Error: 17065, Severity: 16, State: 1. </br>Server Assertion: File: \<FileName>, line = \<LineNumber> Failed Assertion = 'false' Invalid comparison due to NO COLLATION.| SQL Server Engine | Programmability | All |

support/sql/releases/sqlserver-2019/cumulativeupdate27.md

@@ -16,7 +16,7 @@ _Version:_   15.0.4375.4
 
 ## Summary
 
-This article describes Cumulative Update package 27 (CU27) for Microsoft SQL Server 2019. This update contains 14 [fixes](#improvements-and-fixes-included-in-this-update) that were issued after the release of SQL Server 2019 Cumulative Update 26, and it updates components in the following builds:
+This article describes Cumulative Update package 27 (CU27) for Microsoft SQL Server 2019. This update contains 13 [fixes](#improvements-and-fixes-included-in-this-update) that were issued after the release of SQL Server 2019 Cumulative Update 26, and it updates components in the following builds:
 
 - SQL Server - Product version: **15.0.4375.4**, file version: **2019.150.4375.4**
 - Analysis Services - Product version: **15.0.35.45**, file version: **2018.150.35.45**
@@ -43,6 +43,12 @@ Microsoft is working on a fix for this issue and it will be available in a futur
 
 [!INCLUDE [patching-error-2019](../includes/patching-error-2019.md)]
 
+### Issue four: Possibility of error 1204 due to disabled lock escalation
+
+SQL Server 2019 CU26 introduced a regression that can disable lock escalation, which causes error 1204 "The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time."
+
+To work around this issue, you can uninstall the CU26 or install the [CU28](cumulativeupdate28.md).
+
 ## Improvements and fixes included in this update
 
 A downloadable Excel workbook that contains a summary list of builds, together with their current support lifecycle, is available. The Excel file also contains detailed fix lists for SQL Server 2022, SQL Server 2019, and SQL Server 2017. [Select to download this Excel file now](https://aka.ms/sqlserverbuilds).
@@ -62,7 +68,6 @@ For more information about the bugs that are fixed and enhancements that are inc
 | <a id=3088136>[3088136](#3088136) </a> | Fixes an assertion dump issue (Location: hadrlogcapture.cpp:\<LineNumber>; Expression: m_pFsManager->GetEnqueuedBlockId () < capturedLogBlockId \|\| capturedLogBlockId == m_pDbPartner->GetFirstLogBlockIdToCapture ()) that you encounter when there are FILESTREAM transactions in an Always On availability group (AG). | SQL Server Engine | High Availability and Disaster Recovery | All|
 | <a id=3157054>[3157054](#3157054) </a> | Adds performance monitor counters to the cluster log report when the health check timeout is reported. | SQL Server Engine | High Availability and Disaster Recovery | Windows|
 | <a id=3207518>[3207518](#3207518) </a> | [FIX: Memory exceeds the configured limits that are specified by memory.memorylimitmb in SQL Server (KB5042369)](../sqlserver-2022/memory-exceed-configured-limits-memory-memorylimitmb.md) | SQL Server Engine | Linux | Linux|
-| <a id=3282395>[3282395](#3282395) </a> | Fixes the following error 1204 that you encounter when lock escalation doesn't occur if you apply the fix of [Bug 2830668](cumulativeupdate26.md#2830668): </br></br>SQL Server Database Engine cannot obtain a LOCK resource at this time. | SQL Server Engine | Metadata | All |
 | <a id=2955030>[2955030](#2955030) </a> | Fixes an assertion failure (Location: sosmemobj.cpp:2744; Expression: pvb->FInUse()) in `CVariableInfo::PviRelease` that you encounter when you use UTF-8 collations and the `WITH RESULT SETS` clause. | SQL Server Engine | Programmability | All|
 | <a id=2962248>[2962248](#2962248) </a> | Fixes an issue in which change tracking auto cleanup consumes CPU in cycles every 30 minutes even if change tracking isn't enabled on any databases. </br></br>**Note**: After applying the fix, if you see some rows in `sys.syscommittab` or `dbo.MSchange_tracking_history` tables in databases where change tracking is disabled, you need to re-enable and then disable change tracking on these databases. This will clean all tracking data. For more information, see [Enable and Disable Change Tracking](/sql/relational-databases/track-changes/enable-and-disable-change-tracking-sql-server).| SQL Server Engine | Replication | All|
 | <a id=3015695>[3015695](#3015695) </a> | Fixes the following error that you encounter when running `sys.sp_flush_CT_internal_table_on_demand` in a SQL Server instance that has the Case-sensitive (_CS) collation option: </br></br>Msg 137, Level 15, State 2, Procedure sp_ManualCTCleanup, Line \<LineNumber> [Batch Start Line 3] </br>Must declare the scalar variable "@TableName". </br>Msg 137, Level 15, State 2, Procedure sp_ManualCTCleanup, Line \<LineNumber> [Batch Start Line 3] </br>Must declare the scalar variable "@TableName". </br>Total rows deleted: (null). </br>Total rows deleted: (null). | SQL Server Engine | Replication | All|

support/sql/releases/sqlserver-2019/cumulativeupdate28.md

@@ -16,7 +16,7 @@ _Version:_   15.0.4385.2
 
 ## Summary
 
-This article describes Cumulative Update package 28 (CU28) for Microsoft SQL Server 2019. This update contains 11 [fixes](#improvements-and-fixes-included-in-this-update) that were issued after the release of SQL Server 2019 Cumulative Update 27, and it updates components in the following builds:
+This article describes Cumulative Update package 28 (CU28) for Microsoft SQL Server 2019. This update contains 13 [fixes](#improvements-and-fixes-included-in-this-update) that were issued after the release of SQL Server 2019 Cumulative Update 27, and it updates components in the following builds:
 
 - SQL Server - Product version: **15.0.4385.2**, file version: **2019.150.4385.2**
 - Analysis Services - Product version: **15.0.35.48**, file version: **2018.150.35.48**
@@ -78,6 +78,8 @@ For more information about the bugs that are fixed and enhancements that are inc
 | <a id=3278707>[3278707](#3278707) </a> | Fixes the following error that you encounter during a Volume Shadow Copy Service (VSS) restore on a SQL Server instance that has previously deleted databases: </br></br>Volume Shadow Copy Service error: Unexpected error calling routine GetVolumePathName is fail on the path \<PathName> ... The system cannot find the file specified.| SQL Server Engine | Backup Restore| Windows|
 | <a id=3285766>[3285766](#3285766) </a> | Fixes an issue in which the SQL Server Launchpad service can't shut down properly when certain errors occur during startup.| SQL Server Engine | Extensibility | Windows|
 | <a id=3323675>[3323675](#3323675) </a> | Fixes a latch time-out issue that you encounter when fetching the next value for sequence objects, which is due to self-deadlock during lock escalation. | SQL Server Engine | Metadata| All|
+| <a id=2830668>[2830668](#2830668) </a> | Fixes a latch time-out issue that you encounter when fetching the next value for sequence objects, which is due to self-deadlock during lock escalation. | SQL Server Engine | Metadata| All |
+| <a id=3282395>[3282395](#3282395) </a> | Fixes the following error 1204 due to unintentionally disabled lock escalation regression introduced in [CU26](cumulativeupdate26.md).: </br></br>SQL Server Database Engine cannot obtain a LOCK resource at this time. | SQL Server Engine | Metadata | All |
 | <a id=3296380>[3296380](#3296380) </a> | Fixes an issue in which PolyBase throws the following error at service startup if the SQL Server instance is configured to listen on multiple TCP ports: </br></br>System.ArgumentException: Unable to parse port, instance = '\<InstanceName>', text = '\<Text>'| SQL Server Engine | PolyBase| All|
 | <a id=3312936>[3312936](#3312936) </a> | Fixes a non-yielding scheduler dump issue that you might encounter when forcing a query plan in the Query Store (QDS). | SQL Server Engine | Query Optimizer | All|
 | <a id=3312950>[3312950](#3312950) </a> | Fixes an issue in which error 18752 occurs and transactional replication stops working when you use a heavy workload in combination with availability groups and after a failover occurs. </br></br>Error message: </br></br>Only one Log Reader Agent or log-related procedure (sp_repldone, sp_replcmds, and sp_replshowcmds) can connect to a database at a time. If you executed a log-related procedure, drop the connection with session ID \<SessionID> over which the procedure was executed or execute sp_replflush over that connection before starting the Log Reader Agent or executing another log-related procedure. | SQL Server Engine | Replication | Windows|