Update

KB5046365: Cumulative Update 29 for SQL Server 2019

KB5046365 - Cumulative Update 29 for SQL Server 2019

Improvements and fixes included in this update

3426566
Fixes an issue in which Data Analysis Expressions (DAX) queries that use SUMMARIZECOLUMNS and ROLLUPGROUP with multidimensional models might produce incorrect results when running multiple queries that have different sub-selects without clearing the cache, which causes inaccurate totals starting from the second query.

3515480
Adds SQL2019_SSIS.cat, a digitally-signed catalog file in %SystemRoot%\\System32\\CatRoot\\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}, to sign Attunity.SqlServer.CDCControlTask.dll, Attunity.SqlServer.CDCDesign.dll, Attunity.SqlServer.CDCSplit.dll, Attunity.SqlServer.CDCSrc.dll and their resource assemblies for catalog signing.

3354260
Fixes a domain account authentication issue in the configuration tool by adding an auto-retry method to the account validation part, which will use the UPN format and try to authenticate using three separate authentication methods after the authentication fails in SAM format and default.

3459328
Fixes an issue in which the SQL Server Volume Shadow Copy Service (VSS) Writer can't freeze the database during a VSS-based backup. For more information, see known issue three of SQL Server 2019 CU28.

3539961
Fixes an issue in which database striped backups using virtual device interface (VDI) tools might fail to restore with error 3456.

3287653
Fixes an assertion failure (Location: ListenerSpec.cpp:480; Expression: totalUsed + cbListenerName
3407955
Fixes an issue in which a log backup stops responding on the primary replica after the secondary replica restarts if no additional workloads exist on the primary database.

3418490
Fixes a patching error that you encounter in secondary replicas of an availability group with databases that have SQL replication, change data capture (CDC), or SQL Server Integration Services database (SSISDB) enabled. For more information, see known issue two of SQL Server 2019 CU28 or known issue three of SQL Server 2019 CU27.

3336595
Adds a validation for the MODEL parameter when running PREDICT to avoid errors due to the input of wrong models.

3362873
Fixes an issue with checkpoint operation in which the following error 2601 occurs when SQL Server tries to perform a checkpoint operation on the database that has change tracking enabled:

<datetime> Error: 2601, Severity: 14, State: 1.
<datetime> Cannot insert duplicate key row in object '<objectname>' with unique index '<indexname>'. The duplicate key value is <keyvalue>.

3419782
Allows you to disable OLE DB streaming by passing -UseOledbStreaming 0 for the Replication Distribution Agent to avoid the error mentioned in Error message when you run the Distribution Agent in SQL Server.

3466004
Fixes an issue in which the full-text auto crawl monitor is aborted when you use full-text search.

3540450
Makes trace flag 7617 available to skip dropping full-text index fragments marked as deletion during a database recovery process.

3495196
Fixes an issue in which the SQL Server error log might include invalid characters for SQL Server Agent login attempts when the Agent runs a job on a scheduler configured to run automatically once the Agent starts.

3370476
Adds trace flag 6981 to handle large objects (LOBs) when rebuilding the index that has an assertion issue (Location: blobbase.cpp:345; Expression: IS_ON (BLB_TI_END, m_status)). After turning on this trace flag and rebuilding the affected index, the assertion dump shouldn't be generated again.

3409332
Fixes an issue in which table and column names that are read from database metadata aren't correctly quoted in some cases when building internal SQL Server batches in stored procedures that manage temporal tables. After applying the fix, quoting is completed correctly.

3180085
Fixes a performance issue that you might encounter only when sp_lock is called frequently from multiple connections, which might cause a memory leak. The memory isn't cleaned up until you restart the SQL Server service.
Note: You need to turn on trace flag 15915.

3417392
Fixes a contention issue with high KTM_RECOVERY_MANAGER wait times that you might encounter when running XA distributed transactions.
Note: You need to turn on trace flag 8531 as a startup trace flag.

Version: Update 29 (15.0.4405.4) Link
Receive Important Update Messages Stay tuned for upcoming Microsoft SQL Server 2019 updates

Was the content helpful to you?

Advertisement Advertise here?
Udemy IT certification ad