Thanks to the quarantine, Microsoft developers are spending dramatically less time at the water cooler, and they’ve passed the savings on to you. Now, they’re locked up at home, forced to do nothing but fix bugs all day. I’m not sure whether to laugh or cry.
As a result, just nineteen days after the last update, another one. Fixes include:
- Scalar UDF inlining issues – memory leaks, incorrect results
- Performance fixes: severe spinlock contention, incorrect stats, better estimations with UPPER/LOWER/RTRIM
- Crash reductions: crash when you query persisted computed columns, non-yielding scheduler with memory-optimized databases, stack dumps when change tracking auto cleanup fails, background tasks fail when you hit 32K sessions,
- Availability Groups fixes: non-yielding scheduler with Availability Groups, missing log block that causes log rescan,
- Polybase fixes: error, error on the wall
Go grab SQL Server 2019 Cumulative Update 4.
Despite the many bug fixes to UDF inlining, this one still isn’t fixed: https://social.msdn.microsoft.com/Forums/en-US/7d6df408-4c65-42f4-9666-2db0623100f8/nonyielding-scheduler-on-sql-server-2019?forum=sqldatabaseengine&prof=required