SQLServerCentral Editorial

The Ad Hoc Change

Almost every DBA will be asked to change data in production at some point. Too often we don't have the tools to allow users to correct errors, but when you make changes, Steve Jones reminds you that you need to be careful and still have a process.

External Article

Using Extended Events to troubleshoot SQL Server issues

As a DBA, you'll encounter elusive performance, connectivity and locking problems that you'll need to troubleshoot. There are many tools that you can use such as Profiler. In addition to these tools, SQL Server 2008 offers extended events ("XEvents"), which you can use as a powerful tracing system. By default, the "system_health" extended events session is always on, and can provide you help to locate the source of trouble much faster.

Blogs

Webinar: Navigating the Database Landscape in 2026

By

For a number of years, we’ve produced the State of the Database Landscape report,...

Claude AI Convinced Me Not to Build an iPad App

By

I coach volleyball and I do a lot of stat stuff on paper. I...

A New Word: Dolorblindness

By

dolorblindness – n. the frustration that you’ll never be able to understand another person’s...

Read the latest Blogs

Forums

Data Warehouse Toolkit meets Star Schema: The Complete Reference

By pietlinden

Is there a good syllabus for reading these two together? (Yes, it's called the...

GPX distance and time analysis in SQL Server

By Cláudio Tereso

Comments posted to this topic are about the item GPX distance and time analysis...

The DBA is Dead; Long Live the DBA

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The DBA is Dead; Long...

Visit the forum

Question of the Day

Changing the AG Listener

In SQL Server 2025, if I want to remove an IP from a listener, what do I do?

See possible answers