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

Five Ways Redshift Serverless Quietly Eats Your Budget

By

It is Friday, the queries are running, and nobody is watching the bill. That...

A Career of Memories

By

Annabel retired from Redgate Software this week. Across most of my career at Redgate,...

Rethinking Index Maintenance: Why avg_fragmentation_in_percent Is Outdated and What You Should Do Instead

By

As a SQL Server DBA with years of experience tuning production environments, I’ve seen...

Read the latest Blogs

Forums

Changes, Happiness, and a Few Tears

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Changes, Happiness, and a Few...

BCP on Linux

By Steve Jones - SSC Editor

Comments posted to this topic are about the item BCP on Linux

You Probably Don't Need a Vector Database

By Kumar Abhishek

Comments posted to this topic are about the item You Probably Don't Need a...

Visit the forum

Question of the Day

BCP on Linux

When running bcp on Linux, what is the field terminator?

See possible answers