May 31, 2013 at 5:46 am
Hello,
My error log says that the log file of one of my DB was full. Now when I check its 99% free. I backup log at regular interval it just happend in between the two log backups.
My question is that, is there any way to find why the log had grown at that particular time ?
Thanks in advance.
Smith.
May 31, 2013 at 6:49 am
June 1, 2013 at 12:44 pm
I have a default trace running 24/7 that I can use to troubleshoot. You could set one up for the future. Then look at activity in the timeframe between log backups and maybe you will see something useful. Also, you could run transaction log backups more frequently.
June 2, 2013 at 11:24 pm
homebrew01 (6/1/2013)
I have a default trace running 24/7 that I can use to troubleshoot. You could set one up for the future. Then look at activity in the timeframe between log backups and maybe you will see something useful. Also, you could run transaction log backups more frequently.
Running 24/7 trace on DB with heavy transactions won't be advisable is it ?
June 2, 2013 at 11:31 pm
Unless you disabled the default trace, it is already running.
The trace is light weight and does not appreciably affect system performance (or at least in my experience).
June 3, 2013 at 8:33 am
I meant to say I have a server side trace running. I did not make any changes to the system default trace which is also running.
June 3, 2013 at 8:38 am
The default trace captures file growths, iirc.
June 3, 2013 at 10:43 pm
Thank you all. That clarifies. Let me check what's available there.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply