Sample Chapters

External Article

Developing Modifications that Survive Concurrency

  • Article

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.

2010-07-09

3,657 reads

Blogs

SQL Server 2025 Generally Available

By

This was announced last week at Microsoft Ignite and it's been covered by others...

Chatting with Power BI: Who Benefits from This Conversation?

By

"Dave: Open the pod bay doors, HAL.HAL: I’m sorry, Dave. I’m afraid I can’t...

A Quick Look at Redgate Data Modeler

By

Redgate acquired a data modeling tool from Vertabelo recently and I wanted to explore...

Read the latest Blogs

Forums

Steps for Installing AlwaysOn Availability Groups - SQL 2019

By Ginger Daniel

Comments posted to this topic are about the item Steps for Installing AlwaysOn Availability...

SQL Server 2022 order by bug?

By hugo-939487

Hi, I was using order by on a column with characters and saw something...

SQL Server 2025 Build List

By Steve Jones - SSC Editor

Comments posted to this topic are about the item SQL Server 2025 Build List

Visit the forum

Question of the Day

Getting The Database Name

I run this code to connect to SQL Server 2022 from the command line.

sqlcmd -S localhost -E
At the command line, I run these two commands:
SELECT ORIGINAL_DB_NAME()
GO
What is returned?

See possible answers