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,167 reads

Blogs

Rolling Back a Broken Release

By

We had an interesting discussion about deployments in databases and how you go forward...

A bespoke reporting solution doesn’t have to cost the earth

By

You could be tolerating limited reporting because there isn’t an off the shelf solution...

Presenting with Visual Studio Code

By

A while back I wrote a quick post on setting up key mappings in...

Read the latest Blogs

Forums

Cross-DB Ownership Chaining problem

By Johan Bijnens

We want to setup a gateway db to host stored procedures which use tables...

Lots of FKs

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Lots of FKs

Real-time On-prem SQL Server Data in Excel – Over the Internet

By Cláudio Tereso

Comments posted to this topic are about the item Real-time On-prem SQL Server Data...

Visit the forum

Question of the Day

Lots of FKs

In SQL Server 2025, what are the most outgoing and incoming FK references a table can have?

See possible answers