Gail Shaw

  • Interests: Computer Graphics, Aikido, Roleplaying

SQL Server Transaction Log Management eBook Download

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.

You rated this post out of 5. Change rating

2012-11-12

4,446 reads

Blogs

Speaking at SQL Saturday Austin 2025

By

SQL Saturday Austin 2025 is in just a few days. I am honored to...

Updating SSMS is Easy (w/ v21)

By

I’ve been using the SSMS preview for v21. This is the next evolution of...

Execute Fabric Data Pipeline from Azure Data Factory

By

In the blog post Call a Fabric REST API from Azure Data Factory I...

Read the latest Blogs

Forums

The Long Running Backup

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Long Running Backup

Interview Tips

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Interview Tips

importing from PowerQuery... but with multiple powerqueries

By pietlinden

I finally got the PowerQuery source to "show" in SSIS (so I can see...

Visit the forum

Question of the Day

The Long Running Backup

I have a long running backup of the Sales database during a maintenance window that is going to take another 2 hours to complete on SQL Server 2022. I also need to perform some proactive work and add another file (ndf) to the Sales database to handle the expected growth of the next month. Can I do both simultaneously?

See possible answers