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

VPN + SQL Server Connections: Why Long-Working Setups Suddenly Fail with Msg 10054 and “Connection Broken”

By

Over the past few weeks, I’ve been contacted by multiple customers experiencing the same...

Future IT Roles – Agentic Architect and AI Boom!!

By

These days everything is changing to AI World, IT roles are getting changed and...

Free Webinar about Columnstore Indexes

By

I’m doing a small series on indexing basics for SQL Server, and on May...

Read the latest Blogs

Forums

There's Too Much to Learn

By Steve Jones - SSC Editor

Comments posted to this topic are about the item There's Too Much to Learn

How to Calculate Distance Between Coordinates in SQL Server

By Imran2629

Comments posted to this topic are about the item How to Calculate Distance Between...

SSoL Support on the OS

By Steve Jones - SSC Editor

Comments posted to this topic are about the item SSoL Support on the OS

Visit the forum

Question of the Day

SSoL Support on the OS

On which Linux versions is SQL Server 2025 on Linux supported?

See possible answers