Gail Shaw

  • Interests: Computer Graphics, Aikido, Roleplaying

Stairway to Transaction Log Management

Stairway to Transaction Log Management in SQL Server, Level 6: Managing the Log in BULK_LOGGED Recovery Model

A DBA may consider switching a database to the BULK_LOGGED recovery model in the short term during, for example, bulk load operations. When a database is operating in the BULK_LOGGED model these, and a few other operations such as index rebuilds, can be minimally logged and will therefore use much less space in the log

(2)

You rated this post out of 5. Change rating

2025-07-30 (first published: )

6,049 reads

Blog Post

Pluralsight Free April

It’s a few days into April, but not too late I hope to mention that Pluralsight is offering their entire library, free to new accounts, for the month of...

2020-04-16 (first published: )

523 reads

Blog Post

Pluralsight Free April

It’s a few days into April, but not too late I hope to mention that Pluralsight is offering their entire library, free to new accounts, for the month of...

2020-04-07

9 reads

Blogs

Programmatically Retrieving MLV Lineage and Refresh Times

By

Materialized lake views (MLVs) in Microsoft Fabric are an effective way to implement medallion...

SWAG Saves the Day

By

PASS Summit East is in one week. I was on the road last week...

Upgrading SQL Server Containers on the Laptop

By

I don’t have SQL Server installed on my laptop. In an effort to keep...

Read the latest Blogs

Forums

Increase Deadlock Detection

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Increase Deadlock Detection

A Tool is Better than a Script

By Steve Jones - SSC Editor

Comments posted to this topic are about the item A Tool is Better than...

Understanding Deadlock Victim Selection in SQL Server

By john.martin

Comments posted to this topic are about the item Understanding Deadlock Victim Selection in...

Visit the forum

Question of the Day

Increase Deadlock Detection

How can I alter the deadlock detection interval to 2 seconds instead of 5 seconds on my SQL Server 2025 instance?

See possible answers