Breaking News: SQL 2019 CU16 Changes Backup Formats, Can Break Log Shipping.
The newest Cumulative Update for SQL Server 2019 has this gem in the release notes:
This is a massive problem if:
The newest Cumulative Update for SQL Server 2019 has this gem in the release notes:
This is a massive problem if:
You reported it here in the comments, and over at SQLServerUpdates, and in this DBA.StackExchange.com question.
The official word is in: yep, SQL Server 2019 Cumulative Update 2 breaks Agent jobs on some servers, causing them not to run.
The short story: if you drop an index on an indexed view, queries on the Always On Availability Groups replicas that point to that indexed view will cause memory dumps. The long story: to reproduce - AND DO NOT DO THIS IN PRODUCTION - on the primary, create a couple of tables, an indexed view,…
SQL Server Management Studio 17.5 is out, and new in this release is a SQL Data Discovery & Classification feature. The idea is that it'll scan your database, identify columns containing potentially sensitive data, and help you become compliant with regulations like PCI, HIPAA, and GDPR.
Let's see how it works on the Stack Overflow public data dump.
Normally, when you use Transparent Data Encryption (TDE) to secure your database at rest, you can't get backup compression. Encrypted data basically looks like random data, and random data doesn't compress well.
SQL Server 2016 introduced the ability to compress your TDE databases. Yay!
I often hear companies say, "We can never ever go down, so we'd like to implement Always On Availability Groups."
Let's say on January 1, 2016, you rolled out a new Availability Group on SQL Server 2014. It's the most current version available at the time, and you deploy Service Pack 1, Cumulative Update 4 (released 2015/12/22). You're fully current, and it's a stable engine from 2014 - how many more bugs can they find, right?
If you're using SQL Server 2016's awesome new feature, Query Store, there's a new bug with automatic cleanup. Books Online explains: Automatic data cleanup fails on editions other than Enterprise and Developer. Consequently, space used by the Query Store will grow over time until configured limit is reached, if data is not purged manually. If…
Just announced on the Microsoft Release Services blog, if you run a SELECT query with the NOLOCK hint and your query goes parallel, it can block other queries.
This is a bug, and it will be fixed soon, but it is a very big deal for people who think NOLOCK means, uh, NOLOCK.
In the on-premises, boxed-product version of SQL Server, you can build your own CLR assemblies and call them from your T-SQL code.
For years, this feature was missing from Azure SQL DB - Microsoft's platform-as-a-service database offering - and users voted that they wanted it.
Yesterday, Microsoft announced availability of Service Pack 1, saying: As part of our continued commitment to software excellence for our customers, this upgrade is available to all customers with existing SQL Server 2014 deployments via the download links below. Yeah, about that commitment to software excellence. This morning, the download is gone: Notice: The SQL SSIS…
As a DBA, you're responsible for identifying necessary updates to keep your SQL Servers healthy. Your business may have some mandates about the frequency of patches, but even if they don't, you have a duty to look out for Cumulative Updates, Service Packs, and out of band hotfixes that can prevent downtime and prevent performance problems. It's your task to test and apply them as needed.
If you're using AGs, don't apply these patches:
SQL 2012 SP2 CU3
SQL 2012 SP2 CU4
SQL 2014 CU5