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

A New Word: Dolorblindness

By

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

Claude Code Helps Analyze Test Data Manager Log Files

By

I had a customer ask about analyzing their Test Data Manager (TDM) usage to...

PowerPoint to HTML with Claude AI

By

I had an idea for an animated view of a sales tool, and started...

Read the latest Blogs

Forums

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...

Changing the AG Listener

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Changing the AG Listener

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