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

An LLM Saved My ATtiny85 From Certain Death

By

I almost ordered parts for a circuit that would have destroyed itself the instant...

I recommend Smart Brevity (book) for communications

By

Following the advice in Smart Brevity improves communication.

SQL Server 2025 Developer Edition – One size fits all

By

Microsoft has released SQL Server 2025, bringing big improvements to its main database engine....

Read the latest Blogs

Forums

Which Table I

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Which Table I

Using Python notebooks to save money in Fabric: The Fabric Modern Data Platform

By John Miner

Comments posted to this topic are about the item Using Python notebooks to save...

Your AI Successes

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Your AI Successes

Visit the forum

Question of the Day

Which Table I

I have this code in SQL Server 2022:

CREATE SCHEMA etl;
GO
CREATE TABLE etl.product
(
    ProductID INT,
    ProductName VARCHAR(100)
);
GO
INSERT etl.product
VALUES
(2, 'Bee AI Wearable');
GO
CREATE TABLE dbo.product
(
    ProductID INT,
    ProductName VARCHAR(100)
);
GO
INSERT dbo.product
VALUES
(1, 'Spiral College-ruled Notebook');
GO
CREATE OR ALTER PROCEDURE etl.GettheProduct
AS
BEGIN
    SELECT  ProductName
    FROM product;
END;
GO
When I execute this code as a user whose default schema is dbo and has rights to the tables and proc, what is returned?

See possible answers