

Thus, unexpected blocking occurs on the string-type column that has the columnstore index. The NOLOCK hint still requests the IS Object lock. Thus, unexpected blocking occurs on the string-type column that has the columnstore index. The READ_COMMITTED_SNAPSHOT isolation level still requests the IS Object lock. Transactional replication fails with errors 1231 when the replication is enabled on memory optimized tables with computed columns and index on nullable columns respectively. Improvement: Add new Azure SQL Database service tier options to the Stretch Database featureįIX: Changes aren't applied to a newly added article in a peer-to-peer topology with a custom port For more information, contact Customer Support Services. Internal Query Processor Error: The query processor could not produce a query plan. Additionally, the following error 8624 occurs: In Microsoft SQL Server 20, an index creation over a persisted computed column and partition function fails. Note If you don't apply this SQL Server cumulative update, you can use -ASCOLLATION on the command line or UI as a workaround.įIX: Access violation when you use the query_post_execution_plan_profile XEvent and reuse the same execution plan The installation of Microsoft SQL Server 2019 that uses the configuration file ignores the value for the ASCOLLATION parameter and falls back to the system default locale. Note You may see this issue when the number of logical processors is high (larger than 32), and the concurrency jobs are also very high.įIX: Installing SQL Server CUs may trigger IndexOutOfRangeException Unable to start execution of step 1 (reason: Error authenticating proxy, system error: The user name or password is incorrect.). Unable to start execution of step 1 (reason: Error authenticating proxy, system error: ConnGetProxyPassword). The Excel file also contains detailed fix lists for SQL Server 2019 and SQL Server 2017. Improvements and fixes included in this updateĪ downloadable Excel workbook that contains a summary list of builds, together with their current support lifecycle, is available.

There are no known issues in this cumulative update. This update contains 20 fixes that were issued after the release of SQL Server 2019 Cumulative Update 17, and it updates components in the following builds: This article describes Cumulative Update package 18 (CU18) for Microsoft SQL Server 2019. How to obtain or download this or the latest cumulative update package

Improvements and fixes included in this update
