External Article

Developing Modifications that Survive Concurrency

You can create a database under the assumption that SQL looks after all the problems of concurrency. It will probably work fine under test conditions: then, in the production environment, it starts losing data in subtle ways that defy repetition. It is every Database Developer's nightmare. In an excerpt from his acclaimed book, Alex Kuznetsov explains why it happens, and how you can avoid such problems.

Blogs

Programmatically Retrieving MLV Lineage and Refresh Times

By

Materialized lake views (MLVs) in Microsoft Fabric are an effective way to implement medallion...

SWAG Saves the Day

By

PASS Summit East is in one week. I was on the road last week...

Upgrading SQL Server Containers on the Laptop

By

I don’t have SQL Server installed on my laptop. In an effort to keep...

Read the latest Blogs

Forums

Increase Deadlock Detection

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Increase Deadlock Detection

A Tool is Better than a Script

By Steve Jones - SSC Editor

Comments posted to this topic are about the item A Tool is Better than...

Understanding Deadlock Victim Selection in SQL Server

By john.martin

Comments posted to this topic are about the item Understanding Deadlock Victim Selection in...

Visit the forum

Question of the Day

Increase Deadlock Detection

How can I alter the deadlock detection interval to 2 seconds instead of 5 seconds on my SQL Server 2025 instance?

See possible answers