Gail Shaw

  • Interests: Computer Graphics, Aikido, Roleplaying

SQLServerCentral Article

SQL Server Transaction Log Management by Tony Davis and Gail Shaw

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.

(2)

You rated this post out of 5. Change rating

2013-08-26

7,195 reads

Blogs

Upgrading SQL Server Containers on the Laptop

By

I don’t have SQL Server installed on my laptop. In an effort to keep...

How to Find Expensive Queries in Amazon Redshift

By

Slow-running queries can degrade your Redshift cluster’s performance and lead to increased costs. Identifying...

The Notification Trap: How Input Fatigue Is Killing Deep Work in Tech

By

If you've been here before, you know this blog is usually about SQL Server,...

Read the latest Blogs

Forums

Nomor qlola bri

By marketing99

QLola BRI Anda bermasalah? Hubungi WhatsApp 08136035412 untuk mendapatkan bantuan profesional dengan proses yang...

Nomor cs qlola bri berapa

By marketing99

Untuk bantuan QLola BRI, silakan hubungi WhatsApp 08136035412. Melayani kendala akun, transaksi, dan informasi...

Nomor wa Qlola bri

By marketing99

Kini bantuan QLola BRI bisa diakses lebih mudah lewat WhatsApp 08136035412. Tanpa antri, cukup...

Visit the forum

Question of the Day

How Long is a Long I/O?

In SQL Server 2025, a long I/O is recorded in the error log with message 833. How long much an I/O request be outstanding before this message is written to the log?

See possible answers