SQLServerCentral Article

SQL Server Transaction Log Management by Tony Davis and Gail Shaw

When a SQL Server database is operating smoothly and performing well, there is no need to be particularly aware of the transaction log, beyond ensuring that every database has an appropriate backup regime and restore plan in place. When things go wrong, however, a DBA's reputation depends on a deeper understanding of the transaction log, both what it does, and how it works. An effective response to a crisis requires rapid decisions based on understanding its role in ensuring data integrity.

Blogs

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...

Part 3 of 3: Tuning DiskANN — R, Alpha, L, Beam Width, Recall and Latency

By

In Part 1, we saw how ‘Vamana’ represents vectors as nodes, connects them with...

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