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

Funny Money: #SQLNewBlogger

By

While wandering around the documentation looking for some Question of the Day topics, I...

Why Database AI Agents need Layers?

By

Third part in my Ai series with databases. When building AI solutions within the...

Un-Migrating From the Cloud: T-SQL Tuesday #199

By

This month we have a very interesting invitation from Koen Verbeeck. He has hosted...

Read the latest Blogs

Forums

How Do the Experts Become Experts?

By Kathi Kellenberger

Comments posted to this topic are about the item How Do the Experts Become...

Stairway to Reliable Database Deployments Level 4 – Preparing for Production Deployment

By Massimo Preitano

Comments posted to this topic are about the item Stairway to Reliable Database Deployments...

Secure Communications

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Secure Communications

Visit the forum

Question of the Day

Secure Communications

As of June 2026, what is the best version of TLS to use with SQL Server?

See possible answers