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

Redgate and Rome

By

I’m at the UK Redgate office today, meeting with senior leaders in all areas...

Quick Tip: Check Most DTU Expensive Queries in Azure SQL Database

By

Optimizing Azure SQL Database performance often begins with identifying the most resource-intensive queries. Understanding...

PowerShell Newbie – Variables

By

This is Week 2 of PowerShell Strikes Back – a four-week May series for...

Read the latest Blogs

Forums

SSRS Is Dead. Here Are Your Real Options

By sgharlow

Comments posted to this topic are about the item SSRS Is Dead. Here Are...

The Distance Metric

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Distance Metric

The New Wave of Security Threats

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The New Wave of Security...

Visit the forum

Question of the Day

The Distance Metric

In the new VECTOR_DISTANCE() function in SQL Server 2025, the first parameter is the distance_metric. What is this?

See possible answers