September 4, 2001 at 4:17 pm
We backup the the trans logs hourly on a SQL 2000 server. The size of a particular trans log dump done at Sunday 9pm, was 94KB. This is typical. But one hour later at 10pm, the same trans log dump had a size of 317,368KB! The business is closed on Sunday, expecially labor day weekend. Why is the dump so large?
I have seen this type of occurrence before with other databases as well. It makes one wonder if the trans log dump really is OK.
TIA,
Bill Salkin
September 4, 2001 at 6:08 pm
Did you run a maint task? DBCC, rebuild indexes? If it was just on one db I'd suspect you have a job running some place that does a lot of updates.
September 4, 2001 at 7:48 pm
It must be some type of scheduled task that did this. Index rebuilds would easily do this on a large database. You may want to invest in LogExplorer to see what's eating up your logs if it's real important to you.
Brian Knight
http://www.sqlservercentral.com/columnists/bknight
Brian Knight
Free SQL Server Training Webinars
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply