A colleague asked me a very simple question: “How do I know to use row or page compression in SQL Server?” That’s what this post is for, to help provide some clarity on row versus page compression. You’re welcome.
Every DBA wants to become an expert in query performance troubleshooting. Not every DBA is willing to put in the time and effort it takes to become an expert.
So, while the world’s collective media shine a light on the never-ending list of security breaches, I suggest that there are actually more common, and dare I say, even bigger threats that data professionals need to guard against. Not all data professionals are guilty of every one of these sins; rather, the collection of individuals that comprise modern enterprise IT shops is culpable.
Here is a list of the continuing problems that exist in every IT shop around the world. And they aren’t all new, either.
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.
Over the years I’ve been able to compile a list of issues that I would consider to be common with SQL Server (and other database platforms like Oracle, no platform is immune to such issues). These are the issues that are often avoidable but not always easy to fix once they have become a problem. The trick for senior administrators such as myself is to help teams understand the costs, benefits, and risks of their application design options so as to avoid these common problems. So, here is my list of the top 5 most common problems with SQL Server.
