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

2015-07-17 (first published: )

20,098 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,319 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

2017-02-20 (first published: )

37,185 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

2014-10-17 (first published: )

21,778 reads

Blogs

Excellent article on securing msdb

By

Fabiano Amorim has written an excellent article at Simple Talk on securing msdb. Here's...

T-SQL Tuesday #201: Temp Tables

By

This month we have a new host, which I am grateful for. So many...

When Do You Reach For A #temp Table?

By

I needed to do some research because there is more to #temp tables than...

Read the latest Blogs

Forums

OUTER APPLY Fundamentals: Part 2

By Imran2629

Comments posted to this topic are about the item OUTER APPLY Fundamentals: Part 2

Building Great Software

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Building Great Software

The Range of Customers

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Range of Customers

Visit the forum

Question of the Day

The Range of Customers

I have this data in the OrderHeader table in a SQL Server 2025 database (ordered by CustomerID ASC):

orderid orderdate               customerid complete
3       2025-05-10 00:00:00.0002          1
21      2024-01-10 00:00:00.0003          1
15      2023-10-28 00:00:00.0004   1
13      2025-03-08 00:00:00.0006          1
11      2024-04-02 00:00:00.0007          1
If I run this query, how many rows are returned?
SELECT *
 from dbo.OrderHeader
 where customerid between 3 and '6'

See possible answers