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

Moving On-Prem PostgreSQL to the Cloud: Picking the Right Path for Big Tables

By

Every PostgreSQL migration eventually hits the same fork in the road. The database is...

A Spread of Vacation

By

I’m off on vacation today. Which is a little weird as I just got...

How AgentDBA Identifies Backup Failures

By

Every DBA has a box like this. Sitting untouched for months. Nobody’s proud of...

Read the latest Blogs

Forums

Have you done a Mid year check in?

By Pat Wright

Comments posted to this topic are about the item Have you done a Mid...

From SQL Server On-Premises to Claude Desktop: How I built a Full MCP Pipeline

By Cláudio Tereso

Comments posted to this topic are about the item From SQL Server On-Premises to...

Independence Day 2026

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Independence Day 2026

Visit the forum

Question of the Day

Independence Day 2026

In the original Independence Day movie (1996), what type of computer did Jeff Goldblum use to connect to the alien mainframe? Take a guess, don't look it up or ask AI.

See possible answers