Hi All -
SQL server truncates the Transaction log file to maintain the disk space.
Does anyone have idea what triggers SQL server fired to truncate the log file?
Can we trap that trigger or event so that we can control the transaction log truncation? Can we control it whne it happens?
From R&D I found two Architecture of Transaction log:
1) Transaction Log Logical Architecture
2) Transaction Log Physical Architecture Can you please tell me which log file is in use when we are reading it by using DBCC log('DB_Name',4) command.
DBCC log command read which file?
& which file is truncated by SQL_server.
When doing a truncation log back-up what gets backed-up if the log has been truncated?
What method is Microsoft using in SQL Server 2005 mirroring?
What method are companies such as SQL Server Compare using?
Log files truncation behavior of SQL server doesn’t depends on the recovery model selected by user. I mean to say that Transaction log file gets truncated in every case (Simple/Full/Bulk Logged), it doesn’t depend on the recovery model we selected.
It seems that Transaction log gets truncated in every case...!
Actually, it directly depends on the recovery model. You might want to read up on Recovery Models in Books Online. Do you happen to know what backs up this database, and how often it is doing Log backups?