SQLServerCentral Editorial

Divide and Conquer

Schemas may be largely irrelevant to small databases, where it is no trouble to assign permissions to individual objects, but they are vital for a hard working corporate database that is being actively developed and used by several applications, with thousands of objects that must be assigned the correct permission.

External Article

On Handling Dates in SQL

The handling of dates in TSQL is complex - when SQL Server was Sybase, it was forced by the lack of prevailing standards in SQL to create its own ways of processing and formatting dates and times. Joe Celko looks forward to a future when it is possible to write standard SQL date-processing code with SQL Server.

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