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.

3 (2)

You rated this post out of 5. Change rating

2013-08-26

6,806 reads

Blogs

The Book of Redgate–Being Reasonable

By

As a part of the Book of Redgate, we have a series of (red,...

Azure Data Factory Pipeline Debugging Fails with BadRequest

By

I recently had a new pipeline fail. It was actually a copy of an...

Unlocking Real-Time Financial Insights: The Power of Microsoft Fabric

By

Microsoft Fabric is transforming real-time analytics for financial institutions. It provides a unified data...

Read the latest Blogs

Forums

Count of Distinct Values

By jagjitsingh

Hi If value is 21000030 it should return 4 not 5 . In first...

Joining against min date only

By darrell.woolaver 91826

This is one of those things very hard (for me)to explain in words. See...

Feeling your age? How would you know?

By Louis Davidson (@drsql)

Comments posted to this topic are about the item Feeling your age? How would...

Visit the forum

Question of the Day

Rolling Back CUs

Can I rollback a cumulative update and remove it from my SQL Server instance?

See possible answers