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

Why sys.fn_dblog Is Undocumented And Why It's Still There

By

Why sys.fn_dblog Is Undocumented And Why It's Still There Why sys.fn_dblog...

T-SQL Tuesday #202 SQL Server Outage You’ll Never Forget: A Roundup

By

When I put together the invitation for T-SQL Tuesday #202, I wasn't sure what...

A Last Minute Trip to the EU

By

My life has some crazy travel stretches for sure. Between speaking, office visits, customer...

Read the latest Blogs

Forums

Implementing Type 4 Slowly Changing Dimensions in SQL Server

By Dinesh Asanka

Comments posted to this topic are about the item Implementing Type 4 Slowly Changing...

The Disabled Index

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Disabled Index

Server-Level Table sizes

By Artur Sanin

Comments posted to this topic are about the item Server-Level Table sizes

Visit the forum

Question of the Day

The Disabled Index

I run this code on SQL Server 2022.

CREATE TABLE Drink
(
    drinkid INT NOT NULL
        CONSTRAINT DrinkPK PRIMARY KEY CLUSTERED,
    drinkname VARCHAR(20),
    rating NUMERIC(2, 1)
)
GO

INSERT INTO Drink
(
    drinkid,
    drinkname,
    rating
)
VALUES
(1, 'Margarita', 4.5),
(2, 'Mojito', 4.3),
(3, 'Old Fashioned', 4.7),
(4, 'Martini', 4.4),
(5, 'Cosmopolitan', 4.2)
GO
ALTER INDEX drinkpk ON dbo.drink DISABLE
GO
SELECT * FROM dbo.Drink
GO
What is the result?

See possible answers