November 10, 2008 at 11:14 am
Greetings,
I need to monitor my transaction logs for size and back them up when they exceed that size. I would like to use one alert for this if possible...it just seems sensible. I was thinking of using the "_Total" instance of the "SQL Server Databases" counter and have the name of the afflicted database passed to whatever bit of code (stored proc or something else) as well as the notification sent to the DBAs.
I seem to remember that this is possible but can't seem to find where I read that. Anyone else tackled this monster?
-Wayne
November 10, 2008 at 11:25 am
I would strongly suggest that you schedule the log backups to run at a regular interval (hourly is good) rather than basing it on the log's file size. The point of log backups is for recoverability and to prevent data loss in the case of a disaster. Having the backups occur randomly kinda defeats that point.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 10, 2008 at 11:49 am
you can set an alert on size, but I'm not sure you can pass that to a proc. You can probably get the size in T-SQL, but if you should not be using this to run log backups. Log backups are there for recovery, and not something you should be doing some times and not others. Do them regularly.
If there's a growth issue, this probably won't help you with that as when you exceed the size you might not be able to back it up and clear much space.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply