A-one, and a-two – here’s Cumulative Update 2, or as they say in Mexico, DOS. The fix list is pretty long, and here’s some of the greatest hits:
- DML statements unexpectedly replicated to subscribers
- Query returns incorrect results from nonclustered columnstore index
- Incorrect results are returned when query contains a GROUP BY
- Standard Edition’s Analysis Services ignores the 16GB memory limit
- Query Store returns unusual characters (like Erik Darling) when a JOIN operator is used
- Retention policy doesn’t work when you use Managed Backup to Azure
- Updating while compression is in progress can lead to nonclustered columnstore index corruption
- Access violation occurs when you use TDE and BPE
- Queries that run against Always On Availability Group secondaries always get recompiled
- Memory leak occurs when you use Azure Storage
- Access violation occurs when query contains many COUNT DISTINCT operations
- Access violation occurs if trace flag 4139 is enabled
- High CPU usage after you install SQL Server
- SQL Server doesn’t start after you configure TempDB to use a very small log file
- Access violation on secondary replica when there are too many parallel redo operations
- Query runs slowly when SQL Server uses a hash aggregate in the plan
And many, many more. Go check it out.
This seems like a dumb fix…”Standard Edition’s Analysis Services ignores the 16GB memory limit” … yes MS please take away memory that was forgotten to be locked down.
I wondered how many people were going to catch that, hahaha.
Why Microsoft puts artificial memory limits on any of their SQL Server products is at best questionable. It’s even worse, however, when Microsoft has to put a “fix” in place to bring the Standard Edition of Analysis Service (tabular mode) back down to their artificial 16GB memory limit. Should have left it alone. Was better before the “fix.”
It doesn’t seem like the link to the update is working. Did Microsoft pull it back?