baselines

External Article

Baselining with SQL Server Dynamic Management Views

  • Article

When you're monitoring SQL Server, it's better to capture a baseline for those aspects that you're checking, such as workload, Physical I/O or performance. Once you know what is normal, then performance tuning and resource provisioning can be done in a timely manner before any problems becomes apparent. We can prevent problems by being able to predict them. Louis shows how to get started.

2013-07-30

4,688 reads

Technical Article

Capturing Baselines on SQL Server: Wait Statistics

  • Stairway Step

By capturing baseline data, a well-prepared DBA should get a good idea of what potential issues they will face. In this article Erin Stellato looks at Wait Statistics and what they can tell you about your databases.

You rated this post out of 5. Change rating

2020-06-30 (first published: )

19,975 reads

Technical Article

Capturing Baselines on SQL Server: Where's My Space?

  • Stairway Step

In this article, we'll tackle the topic of monitoring disk space usage. By tracking how much is in use and how much is still available, over time we'll have the data we need for better capacity planning, and can ensure that a database won't ever run out of disk space.

You rated this post out of 5. Change rating

2013-01-23

10,283 reads

Technical Article

Back to Basics: Capturing Baselines on Production SQL Servers

  • Stairway Step

If you have not been capturing baselines on your production servers, then today is the day you can start. This article provides scripts, valid for SQL Server 2005 and higher, which anyone can use to capture basic information about a SQL Server instance.

You rated this post out of 5. Change rating

2020-06-30 (first published: )

37,111 reads

Technical Article

5 Reasons You Must Start Capturing Baseline Data

  • Stairway Step

It is widely acknowledged within the SQL Server community that baselines represent valuable information that DBAs should capture. Unfortunately, very few companies manage to log and report on this information, and DBAs are then forced to troubleshoot from the hip and scramble to find evidence to prove that the database is not the problem. This article will make a compelling argument for why DBAs must start capturing baseline information, and will create a roadmap for subsequent posts.

You rated this post out of 5. Change rating

2020-06-30 (first published: )

21,721 reads

Blogs

Shifting Mindsets: Why FinOps is Essential for Cloud Efficiency

By

As a DevOps practitioner, I’ve always focused on performance, scalability, and automation. But as...

March 2026 SQL Server Security Updates

By

On Patch Tuesday, in addition to OS and Office security patches, Microsoft also released...

How Fabric Mirroring Transformed with SQL Server 2025

By

When mirroring was first released for Azure SQL Database, it used Change Data Capture...

Read the latest Blogs

Forums

Multiple Deployment Processes

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Multiple Deployment Processes

How to Use sqlpackage to Detect Schema Drift Between Azure SQL Databases

By Kunal Rathi

Comments posted to this topic are about the item How to Use sqlpackage to...

Upgrading Admin Queries

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Upgrading Admin Queries

Visit the forum

Question of the Day

Upgrading Admin Queries

I have a query from a former DBA that we run on SQL Server 2025 to check on database metadata. This query references sys.sysaltfiles. I want to refactor this code to be more modern. Which DMV should I reference instead?  

See possible answers