Sample Chapters

External Article

Developing Modifications that Survive Concurrency

  • Article

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.

2010-07-09

3,657 reads

Blogs

T-SQL Tuesday #199 Invitation: Back to on-prem?

By

It’s time for T-SQL Tuesday again! And we’re almost to number 200! T-SQL Tuesday...

Data Skew in Data Engineering: What It Is and How to Fix It

By

You kick off a distributed job expecting it to finish in minutes — but...

Error Deploying GraphQL in Fabric: dm_exec_describe_first_result_set

By

A while ago we suddenly had an error while trying to deploy one Fabric...

Read the latest Blogs

Forums

Fuzzy String Matching in SQL Server 2025

By Daniel Calbimonte

Comments posted to this topic are about the item Fuzzy String Matching in SQL...

Representing Money

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Representing Money

Celebrating 30 years of PostgreSQL, A Thank you message

By Pat Wright

Comments posted to this topic are about the item Celebrating 30 years of PostgreSQL,...

Visit the forum

Question of the Day

Representing Money

Which types of currency does the money data type represent?

See possible answers