PASS Pro Now Available

Welcome to the next evolution of PASS. Unlock exclusive training, discounts, and networking opportunities designed to accelerate your data career. Learn More >

The official PASS Blog is where you’ll find the latest blog posts from PASS community members and the PASS Board. Contributors share their thoughts and discuss a wide variety of topics spanning PASS and the data community.

We've moved!

Looking for the latest blog posts? We've recently moved the PASS Blog to its new home at You can still view older blog posts here but please update your bookmarks so you can continue getting the latest posts from the PASS Blog.

Posts Tagged 'DBA'

We are pleased to present below all posts tagged with 'DBA'. If you still can't find what you are looking for, try using the search box.

Properly Upgrading SQL Server

For several reasons, upgrading to modern versions of SQL Server can be more challenging than it was when you upgraded to SQL Server 2012 or older. 

SQL Server Perfmon Counters that are Still Interesting in 2019

Years ago, my first go-to tool for performance tuning was Performance Monitor: it was available everywhere, worked in all versions, and gave me a lot of useful information without paying for a monitoring tool. Since then, I've moved onwait stats are a much better starting pointbut there are still 3 good Perfmon counters that I rely on.

Finding the Slowest Query in a Stored Procedure

It’s not uncommon to see procedures with hundreds, even thousands of lines of code.  You may have been told which stored procedure runs slow by a user or manager, or you might have found it by looking in SQL Server DMVs.  Either way, once you have detected the offending procedure, where do you start?

The Turbo Button is Here - The Batch Mode on Rowstore Indexes

The introduction of the Batch Execution Mode on the Rowstore Indexes has caused a significant change in how things will work for the big aggregation queries on the Microsoft Data Platform.

Why Queries May Easily Return Incorrect Data in SQL Server

SQL Server has an interesting question when it comes to running multiple queries at the same time. If my session is reading data while other queries are modifying data, what should happen? Should my query hold locks to protect that data? If so, how many locks should it hold, and how long should it hold them for? 

Back to Top