Robert wrote:Just a thought: could it be you have a very long running transaction on your database? If so, two things could result:
1) SQL Server can't truncate the transaction log prior to the start of that transaction, maybe explaining why it's so large;
2) SQL Log Rescue won't show any uncommitted transactions
The transaction log is certainly truncated on a log backup; I don't remember off the top of my head if this also applies to a full backup.
Users browsing this forum: No registered users and 1 guest