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

How to Connect to SQL Server When Nothing Else Works – DAC

By

It's 2 AM. Your phone is going off. Users can't connect to the application,...

Get a Range of Sequence Values: #SQLNewBlogger

By

I discovered a procedure recently that I wasn’t aware of: sp_sequence_get_range. This post looks...

The Agent Era: When “How do I…?” Replaces “Where do I click?”

By

After a year away getting to grips with AI and its application across the...

Read the latest Blogs

Forums

Local Agents

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Local Agents

Detecting Deadlocks

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Detecting Deadlocks

Introducing the Relational Embedding Retrieval Pattern: Storing and Querying Vector Embeddings in SQL Server

By SQL Expert

Comments posted to this topic are about the item Introducing the Relational Embedding Retrieval...

Visit the forum

Question of the Day

Detecting Deadlocks

By default, how often is the SQL Server Database Engine checking for deadlocks?

See possible answers