Hi,
Can anyone explain this counter in detail? I have been unable to find documentation on why a value of say '50' is bad and why '0' is considered OK.
MSSQL Log Truncation
Re: MSSQL Log Truncation
It is not necessarily 'bad', i', '50' is just the default threshold. Depending on your environment, this alert could be be anything from benign to mission critical. This is a better question for you MSSQL admins, as they know the environment and the average rate of logging.
http://technet.microsoft.com/en-us/libr ... 80%29.aspx
http://www.mssqltips.com/sqlservertip/1 ... -counters/
http://technet.microsoft.com/en-us/libr ... 80%29.aspx
http://www.mssqltips.com/sqlservertip/1 ... -counters/
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
Re: MSSQL Log Truncation
Hi,
Thanks for your reply, unfortunately it didn't help however I did find the cause. The 'initial size' setting of the log file was too low therefore the log was being truncated as it was above 70% capacity.
Thanks for your reply, unfortunately it didn't help however I did find the cause. The 'initial size' setting of the log file was too low therefore the log was being truncated as it was above 70% capacity.