SQLServerCentral Editorial

The Train to Katmai

We don't have a release date, the final feature set has yet to be released, but slowly I can see the train building steam. This week I found a number of blogs starting to look at various aspects of SQL Server 2008. If you look through the newsletter, you'll see coverage of data compression, clustering […]

Technical Article

Write custom trace files in TSQL

SQL Server 2005's default trace is great for monitoring system information and for finding out what happened on your server after problems occur. However, there are times when the events that the default captures are not what you need. Here are instructions for how you can create your own trace files in TSQL to catch events on your database machine.

Blogs

Shifting Mindsets: Why FinOps is Essential for Cloud Efficiency

By

As a DevOps practitioner, I’ve always focused on performance, scalability, and automation. But as...

March 2026 SQL Server Security Updates

By

On Patch Tuesday, in addition to OS and Office security patches, Microsoft also released...

How Fabric Mirroring Transformed with SQL Server 2025

By

When mirroring was first released for Azure SQL Database, it used Change Data Capture...

Read the latest Blogs

Forums

XACT_ABORT being set to ON by web services

By zoggling

We have two "identical" instances of an ASP.NET web service (or so I have...

OPENQUERY Flexibility

By Steve Jones - SSC Editor

Comments posted to this topic are about the item OPENQUERY Flexibility

A Full Shutdown

By Steve Jones - SSC Editor

Comments posted to this topic are about the item A Full Shutdown

Visit the forum

Question of the Day

OPENQUERY Flexibility

Which of these are valid OPENQUERY() uses?

See possible answers