Transaction Log

External Article

Optimizing Transaction Log Throughput

  • Article

As a DBA, it is vital to manage transaction log growth explicitly, rather than let SQL Server auto-growth events "manage" it for you. If you undersize the log, and then let SQL Server auto-grow it in small increments, you'll end up with a very fragmented log. This article demonstrates how this can have a significant impact on the performance of any SQL Server operations that need to read the log.

2014-05-27

3,916 reads

External Article

Manual cleanup Change Data Capture for a SQL Server database

  • Article

Kun Lee had a database where the log file kept growing and used 99.99% of the available space. He noticed miscellaneous change data capture objects still in the database as well as open transactions. This was causing his transaction log to continue to grow, but he couldn't disable CDC, because SQL Server thought it was not enabled. Read the full article to see his solution.

2013-09-11

3,682 reads

Blogs

Using CAT for Testing of Data Agents

By

In last months one of the scenarios where you can use AI has been...

Are you getting value from your reporting?

By

Do you spend so long manipulating your data into something vaguely useful that you...

The Book of Redgate: SQL Server Central

By

It was neat to stumble on this in the book, a piece by me,...

Read the latest Blogs

Forums

Foreach Loop still executes after process and delete all the folders

By robink

I have two challenges XML source control not displaying the XML file parent node...

Which 'Where' statement conditional upon a variable

By DaveBriCam

Thanks in advance for any clues on this. I am trying to write a...

Backup to Immutable Storage

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Backup to Immutable Storage

Visit the forum

Question of the Day

Backup to Immutable Storage

In SQL Server 2025, a backup can be made on Azure Immutable Storage. What changes in how the backup is created?

See possible answers