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

The Book of Redgate: Hours

By

I have said and written this many times: Redgate Software is the type of...

How to Check TDE Progress and Elapsed Time in SQL Server

By

How to Check TDE Progress and Elapsed Time in SQL Server ...

PostgreSQL Support in the Data API Builder

By

Next week I’m at VS Live in San Diego (register and join me) and...

Read the latest Blogs

Forums

Squared Values

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Squared Values

I Don't Want To Do XX

By Steve Jones - SSC Editor

Comments posted to this topic are about the item I Don't Want To Do...

Managing Feature Flags with GET_BIT() and SET_BIT() in SQL Server

By john.martin

Comments posted to this topic are about the item Managing Feature Flags with GET_BIT()...

Visit the forum

Question of the Day

Squared Values

What happens when I run this code in SQL Server 2022?

SELECT SQUARE('12')

See possible answers