Transaction Log

Technical Article

Help! My SQL Server Log File is too big!

  • Article

Over the years, I have assisted so many different clients whose transactional log file has become "too large" that I thought it would be helpful to write about it. The issue can be a system crippling problem, but can be easily avoided. Today I'll look at what causes your transaction logs to grow too large, and what you can do to curb the problem.

(3)

You rated this post out of 5. Change rating

2008-10-28

6,699 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