Transaction Log

Stairway to Transaction Log Management

Stairway to Transaction Log Management in SQL Server, Level 9: Monitoring the Transaction Log

  • Stairway Step

Our major goal in terms of log maintenance for all databases under our care is to optimize for write performance, in order to support all activities that require SQL Server to write to the log, including data modifications, data loads, index rebuilds, and so on. However, it's also important to keep an eye on possible log fragmentation, which, as described previously, can affect the performance of processes that need to read the log, such as log backups and the crash recovery process.

5 (1)

2013-04-24

7,231 reads

SQL Server Transaction Log Management eBook Download

SQL Server Transaction Log Management by Tony Davis and Gail Shaw

  • Book

When a SQL Server database is operating smoothly and performing well, there is no need to be particularly aware of the transaction log, beyond ensuring that every database has an appropriate backup regime and restore plan in place. When things go wrong, however, a DBA's reputation depends on a deeper understanding of the transaction log, both what it does, and how it works. An effective response to a crisis requires rapid decisions based on understanding its role in ensuring data integrity.

2012-11-12

4,366 reads

Stairway to Transaction Log Management

Stairway to Transaction Log Management in SQL Server, Level 6: Managing the Log in BULK_LOGGED Recovery Model

  • Stairway Step

A DBA may consider switching a database to the BULK_LOGGED recovery model in the short term during, for example, bulk load operations. When a database is operating in the BULK_LOGGED model these, and a few other operations such as index rebuilds, can be minimally logged and will therefore use much less space in the log

5 (2)

2012-11-07

5,107 reads

External Article

SQL Server Transaction Log Fragmentation: a Primer

  • Article

Generally, you will have no need to worry about the number of virtual log files in your transaction log. However, if you use the default settings for 'auto-grow', you can end up with such 'fragmentation' in your transaction log as to affect performance noticably. How can this be avoided? How can you tell it's a problem? What do you do about it? Greg explains.

2012-11-23 (first published: )

7,126 reads

Blogs

Advent of Code 2022

By

Foreword Advent of Code is an annual event in which participants solve a series of...

Daily Coping 8 Dec 2022

By

Today’s coping tip is to be curious. Learn about a new topic or an...

#PowershellBasics: Warnings and how to hide them.

By

One of my favorite parts of having a new job is that I learn...

Read the latest Blogs

Forums

Problem Importing NULLs in varchar field

By John524

hello, This is something I'm really struggling with and haven't found much when I...

SQL Server 2022 is RTM

By Grant Fritchey

You can get your hands on SQL Server 2022 right now and this forum,...

Blocking

By sqlguru

We were getting constant blocking on the db server. However, after stopping the process...

Visit the forum

Ask SSC Logo Ask SSC

SQL Server Q&A from the SQLServerCentral community

Get answers