External Article

Formatting SQL Code - Part the Second

When you're formatting SQL Code, your objective is to make the code as easy to read with understanding as is possible, in a way that errors stand out. The extra time it takes to write code in an accessible way is far less than the time saved by the poor soul in the future, possibly yourself, when maintaining or enhancing the code. There isn't a single 'best practice, but the general principles, such as being consistent, are well-established. Joe Celko gives his take on a controversial topic.

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