Skip to content

Commit 2678cc9

Browse files
author
Simonx Xu
authored
Update cumulativeupdate20.md
1 parent ce35b3d commit 2678cc9

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

support/sql/releases/sqlserver-2022/cumulativeupdate20.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,12 +43,12 @@ For more information about the bugs that are fixed and enhancements that are inc
4343
|<a id=4100859>[4100859](#4100859) </a> | Fixes an assertion failure (Location:"sql\\ntdbms\\storeng\\dfs\\manager\\blobaccess.cpp":9441; Expression:filepos > protocolHandler->m_maxFilePosSoFar) that you encounter when backing up to S3-compatible object storage fails and then having 20 retries. | SQL Server Engine | Backup Restore| All |
4444
|<a id=4123934>[4123934](#4123934) </a> | Fixes a deadlock issue that results in a non-yielding scheduler and causes the SQL Server instance to stop responding when `control.alternatewritethrough` is set to `1` under low vCPU conditions. | SQL Server Engine | Linux | Linux |
4545
|<a id=4297001>[4297001](#4297001) </a> | Adds memory limit support for Control Groups (cgroups) v2 in Platform Abstraction Layer (SQLPAL). | SQL Server Engine | Linux | Linux |
46+
|<a id=4167049>[4167049](#4167049) </a> | Fixes a non-yielding scheduler dump issue with `qds!CDBQDS::AbortQdsBackgroundTask` that may occur when the list of Query Store (QDS) background tasks is large and either QDS is disabled or SQL Server shuts down. In addition to the dump, you would see the following error messages: </br></br> Error: 1222, Severity: 16, State: 111.</br>Lock request time out period exceeded.</br>Error: 12412, Severity: 16, State: 1.</br>Internal table access error: failed to access the Query Store internal table with HRESULT: 0x80004005| SQL Server Engine | High Availability and Disaster Recovery | All |
4647
|<a id=4257781>[4257781](#4257781) </a> | Fixes an issue in which uninitialized memory is returned in some rare cases when using limited length parameters with `REPLACE` function. | SQL Server Engine | Programmability | All |
4748
|<a id=4277598>[4277598](#4277598) </a> | Fixes an issue in which an access violation dump occurs instead of returning the correct error message when using `PARSE` or `TRY_PARSE` with special floating-point values such as NaN (Not-a-Number) or Infinity as input.| SQL Server Engine | Programmability | All |
4849
|<a id=4053244>[4053244](#4053244) </a> | Fixes an issue in which uninitialized memory can be read in some rare cases when using variable length parameters.| SQL Server Engine | Query Execution | All |
4950
|<a id=4104525>[4104525](#4104525) </a> | Fixes an access violation that you encounter when a query calls a multi-statement table-valued function (MSTVF) that has a common language runtime (CLR) expression in its parameter and triggers interleaved execution.| SQL Server Engine | Query Optimizer | All |
5051
|<a id=4317961>[4317961](#4317961) </a> | Adds support for "**WITH SID=sid, TYPE=[E\|X]**" in the `CREATE USER` syntax in SQL Server 2022 by using trace flag 11953. For more information, see [CREATE USER (Transact-SQL)](/sql/t-sql/statements/create-user-transact-sql#syntax). | SQL Server Engine | SQL Server Engine | All |
51-
|<a id=4167049>[4167049](#4167049) </a> | Fixes a non-yielding scheduler dump issue with `qds!CDBQDS::AbortQdsBackgroundTask` that may occur when the list of Query Store (QDS) background tasks is large and either QDS is disabled or SQL Server shuts down. In addition to the dump, you would see the following error messages: </br></br> Error: 1222, Severity: 16, State: 111.</br>Lock request time out period exceeded.</br>Error: 12412, Severity: 16, State: 1.</br>Internal table access error: failed to access the Query Store internal table with HRESULT: 0x80004005| SQL Server Engine | High Availability and Disaster Recovery | All |
5252
|<a id=4044263>[4044263](#4044263) </a> | Fixes an issue introduced by a previous Windows update that causes restarts and even prevents setup from continuing. After applying this fix, the value of the `PendingFileRenameOperations` registry key is deleted when applying updates to SQL Server. | SQL Setup | Patching| Windows |
5353

5454
## How to obtain or download this or the latest cumulative update package

0 commit comments

Comments
 (0)