More General and Less SQL
Many DBAs liken their roles to being a mechanic, and with everything under the hood of SQL Server these days I think an F1 mechanic is an apt comparison.
Many DBAs liken their roles to being a mechanic, and with everything under the hood of SQL Server these days I think an F1 mechanic is an apt comparison.
Here is a list of the continuing problems that exist in every IT shop around the world. And they aren’t all new, either.
When I hear stories about folks that tried to migrate to Microsoft Azure SQL Database with a brute-force-single-click and failed, I ask several follow up questions. I have found a common pattern in the answers: lack of strategy.
Nobody likes surprises when it comes to upgrading or migrating SQL Server instances. Trace flags get set and forgotten. I’m hoping that this post will help people to remember.
If you still don’t believe that SQL Server 2016 is full of unicorns and rainbows then I would encourage you to try it for yourself.
Here’s an example of something I came across for Azure SQL Database V12 that I don’t see documented anywhere (yet): You can change the compatibility level of an Azure SQL Database.