December 13, 2011 at 10:54 am
I have a database where its log file seems to shrink itself. Our monitoring software (Idera) will inform us when the log file is above %90 full. At this point, it should grow. We have upped the initial size for the log file to 256 MB and autogrowth of 32 MB. However, checking throughout the day, its seems that the inital size of the database drops down to 9 MB. We do not have a SQL Agent job set to shrink this log file. Is there a way that I can check to see what is causing this, maybe through a trace?
December 13, 2011 at 10:55 am
DB in simple mode?
Taking regular log backups?
December 13, 2011 at 11:32 am
Do you have auto-shrink turned on for the database?
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
December 13, 2011 at 11:35 am
It's set to full recovery with hourly log backups.
December 13, 2011 at 11:40 am
jbrown414 (12/13/2011)
It's set to full recovery with hourly log backups.
The log backups "repair" that warning.
Autoshrink would actually make it happen more often. :hehe:
December 13, 2011 at 11:40 am
It is set to auto shrink. :pinch:
Thank you Craig. I will get it turned off.
December 13, 2011 at 12:07 pm
jbrown414 (12/13/2011)
It is set to auto shrink. :pinch:Thank you Craig. I will get it turned off.
LOL, no problem. Sometimes Occam was quite correct. Gotta love inheriting systems and settings... 😉
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply