June 24, 2014 at 2:42 am
Hi all,
From a best practice point of view I know that database log files shouldn't be larger that the actual data file however, I've got a database that's only 595Mb big but has a log file that comes in at 813mb.
Do people think I really need to do anything with the log file (i.e. shrink it) bearing in mind the size of the DB and the fact that it's not having a detrimental performance effect on the server etc? I'm thinking leave it alone personally but figured I'd try to get a consensus.
Many thanks.
email: info@weekendwebdesign.co.uk
Personal Website: http://markallen.co.uk/
Business Website: https://www.weekendwebdesign.co.uk
June 24, 2014 at 2:45 am
What recovery model are you in? If it's Full, are you taking regular log backups?
What do you get if you run this?
SELECT name,log_reuse_wait_desc FROM sys.databases
June 24, 2014 at 2:50 am
Sorry forgot to mention, recovery model is full and t-log backups are taken 5 times daily at 08:00, 11:00, 15:00, 18:00 & 22:00. I restructured the T-log backups a added two new ones into the equation a few months ago to try and sort this issue but it's still happening!
Output from the query for log_reuse_wait_desc = NOTHING'
email: info@weekendwebdesign.co.uk
Personal Website: http://markallen.co.uk/
Business Website: https://www.weekendwebdesign.co.uk
June 24, 2014 at 4:09 am
It should be fine as database size is very small. Also think if you shrink and free some space i.e 300-400 MB how does it help you?
---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
June 24, 2014 at 4:14 am
That was my thinking tbh, I like best practice but sometimes you just have to think whether it's worth following especially on a DB this small that doesn't appear to be having a negative effect on the server.
Cheers for the thoughts and help.
email: info@weekendwebdesign.co.uk
Personal Website: http://markallen.co.uk/
Business Website: https://www.weekendwebdesign.co.uk
June 24, 2014 at 5:22 am
On a database that small... I wouldn't sweat it, but if you are worried, take more frequent log backups. That will reclaim space faster.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply