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

Claude AI Convinced Me Not to Build an iPad App

By

I coach volleyball and I do a lot of stat stuff on paper. I...

A New Word: Dolorblindness

By

dolorblindness – n. the frustration that you’ll never be able to understand another person’s...

Claude Code Helps Analyze Test Data Manager Log Files

By

I had a customer ask about analyzing their Test Data Manager (TDM) usage to...

Read the latest Blogs

Forums

Data Warehouse Toolkit meets Star Schema: The Complete Reference

By pietlinden

Is there a good syllabus for reading these two together? (Yes, it's called the...

GPX distance and time analysis in SQL Server

By Cláudio Tereso

Comments posted to this topic are about the item GPX distance and time analysis...

The DBA is Dead; Long Live the DBA

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The DBA is Dead; Long...

Visit the forum

Question of the Day

Changing the AG Listener

In SQL Server 2025, if I want to remove an IP from a listener, what do I do?

See possible answers