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

Microsoft Build 2026 announcements

By

Once again there were a number of Microsoft Build announcements related to data and...

T-SQL Tuesday #199: Roundup

By

A good week ago I hosted the monthly T-SQL Tuesday blog party. I invited...

No Shortcuts for the SQLCMD Batch Terminator: #SQLNewBlogger

By

I was messing around with SQLCMD and I realized something I hadn’t known. I’ve...

Read the latest Blogs

Forums

Changes, Happiness, and a Few Tears

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Changes, Happiness, and a Few...

BCP on Linux

By Steve Jones - SSC Editor

Comments posted to this topic are about the item BCP on Linux

You Probably Don't Need a Vector Database

By Kumar Abhishek

Comments posted to this topic are about the item You Probably Don't Need a...

Visit the forum

Question of the Day

BCP on Linux

When running bcp on Linux, what is the field terminator?

See possible answers