I have a database that I am backing up the transaction log ever 30 minutes however the log size is always around 850mb regardless if the backup is through the day when work is happening or at 3 am in the morning.
What could be causing this?
I guess there may be some automated data input but is there anything else that would cause the log to be around the same size at every backup.
The recovery mode for the database is FULL.
Answer by Matt Whitfield ·
Just because the log file is a certain size doesn't mean that it is all used.
Check out DBCC SQLPERF (LOGSPACE) and see whether the amount of log used is changing after your backups.
Answer by Rob Farley ·
The fact that your log file is always the same size is really healthy. The log file itself won't shrink unless you ask it to. Truncating won't actually shrink the file, just mark it for re-use. If your log file had filled up, it would be needing to grow. Also, your log backups would be large.
How big are your backups? That's often a nice indication about how much data is in your log file at any point in time.
Another way of checking the size of the log file is within Management Studio. Right-click on the database in question, go to Tasks, Shrink File. Don't actually tell it to shrink anything, just have a look to see what the dialog tells you when you pick Log from the "File Type" combo. It'll probably tell you that the file is 99% empty.