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

From SQL Saturday to Day of Data

By

A behind-the-scenes look at Day of Data Jacksonville 2026, the transition from SQL Saturday,...

PostgreSQL 18 Finally Makes BUFFERS the Default. Here Is Why That Matters

By

You run EXPLAIN ANALYZE on a slow query, stare at the plan, and something...

A New Word: La Guadière

By

la guadière – n. a glint of goodness you notice in something that you...

Read the latest Blogs

Forums

non ascii columns in a utf-8 .txt file

By stan

hi, we couldnt get our upstream data source developers to supply what is sometimes...

PolyBase Trace Flags

By Leo.Miller

Are there any good articles on all the trace flags that are enabled on...

The Data Model Matters

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Data Model Matters

Visit the forum

Question of the Day

Running SQLCMD I

I run the SQLCMD utility as follows:

lcmd -S localhost -E
I then type this (the 1> is the prompt):
1> select @@version go
If I hit enter, what happens?

See possible answers