What part of the SQLDump suggest database corruption? A reader asked, and I show the DbccResults tag in the SQLDump text file that confirms it.
Huge Transaction Log File in SQL Server: Find the Cause
A huge transaction log file has a named reason in log_reuse_wait_desc. This post builds a small demo database, reads that reason, backs up the log and finds the open transaction that holds it. It ends with a one time shrink and a safe growth step.
How an Open Transaction Uses Free Log Space
An open transaction holds free log space hostage. This post runs one transaction in a SIMPLE recovery database and reads the log after the load and after the commit. It explains why the log grows before COMMIT, what ACTIVE_TRANSACTION means, and why a new FULL recovery database behaves like SIMPLE until its first full backup.
Find Who Dropped a Table by Reading the Transaction Log
To find who dropped a table, read the transaction log for the DROPOBJ transaction and look up the login behind its security ID. This post runs that search on a demo database, shows the default trace as a second source when the log has been truncated, and explains what to do when everyone shares one login.







