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

How Fabric Mirroring Transformed with SQL Server 2025

By

When mirroring was first released for Azure SQL Database, it used Change Data Capture...

The DIY Cost of Masking Test Data For Smaller Organizations

By

One of the things I’ve tried hard to do in database development situations if...

T-SQL Tuesday #196 – Two risky career decisions I made

By

The T-SQL Tuesday topic this month comes James Serra. What career risks have you...

Read the latest Blogs

Forums

XACT_ABORT being set to ON by web services

By zoggling

We have two "identical" instances of an ASP.NET web service (or so I have...

OPENQUERY Flexibility

By Steve Jones - SSC Editor

Comments posted to this topic are about the item OPENQUERY Flexibility

A Full Shutdown

By Steve Jones - SSC Editor

Comments posted to this topic are about the item A Full Shutdown

Visit the forum

Question of the Day

OPENQUERY Flexibility

Which of these are valid OPENQUERY() uses?

See possible answers