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

Blogs

Ways to land data into Fabric OneLake

By

Microsoft Fabric is rapidly gaining popularity as a unified data platform, leveraging OneLake as...

A Very Cool Benefit in SSMS 21

By

I saw a post from Erin that Preview 2 is available. I’d gotten a...

AI Helping with an API

By

Can an AI help me with some database API work? Let’s see. This is...

Read the latest Blogs

Forums

How to speed up this query?

By water490

Hi everyone I have a query that is taking a real long time.  It...

The New Log File

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The New Log File

Getting Started with the Data API Builder

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Getting Started with the Data...

Visit the forum

Question of the Day

The New Log File

I have a detached database from SQL Server 2019, called TDE_Primer. This database had a 100MB data file and a 73MB log file. The log file was lost, so I need to run this code:

USE [master]
GO
CREATE DATABASE [TDE_Primer] ON 
( FILENAME = N'C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\DATA\TDE_Primer.mdf' )
 FOR ATTACH_REBUILD_LOG
GO
How big is the new log file?

See possible answers