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

The Book of Redgate–Being Reasonable

By

As a part of the Book of Redgate, we have a series of (red,...

Azure Data Factory Pipeline Debugging Fails with BadRequest

By

I recently had a new pipeline fail. It was actually a copy of an...

Unlocking Real-Time Financial Insights: The Power of Microsoft Fabric

By

Microsoft Fabric is transforming real-time analytics for financial institutions. It provides a unified data...

Read the latest Blogs

Forums

Joining against min date only

By darrell.woolaver 91826

This is one of those things very hard (for me)to explain in words. See...

Feeling your age? How would you know?

By Louis Davidson (@drsql)

Comments posted to this topic are about the item Feeling your age? How would...

Sever Migration

By Arjun SreeVastsva

Hi, one of my server configured with Standard_D64ds_v4 what is next level of version...

Visit the forum

Question of the Day

Rolling Back CUs

Can I rollback a cumulative update and remove it from my SQL Server instance?

See possible answers