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

A New Word: Foilsick

By

foilsick – adj. feeling ashamed after revealing a little too much of yourself to...

Accelerated Database Recovery for tempdb in SQL Server 2025

By

Accelerated database recovery was introduced in SQL Server 2019 and provides fast recovery, instantaneous...

Measuring What Matters: Operationalizing Data Trust for CDOs

By

Trust is the currency of the data economy. Without it, even the most advanced...

Read the latest Blogs

Forums

Create an HTML Report on the Status of SQL Server Agent Jobs

By Nisarg Upadhyay

Comments posted to this topic are about the item Create an HTML Report on...

ETL Framework In Production

By Rahulmsb5

Hello, I am leveraging Python within SQL Server Integration Services (SSIS) packages, primarily through...

SQL Server Ghosts

By Steve Jones - SSC Editor

Comments posted to this topic are about the item SQL Server Ghosts

Visit the forum

Question of the Day

SQL Server Ghosts

For Halloween, what are ghost records?

See possible answers