Event driven log backup?

[Fred Prose]

Has anyone explored a process whereby the Transaction Log would be
backup up based upon a defined threshold, ie. 75% full? All the
research against news group posts and SQL2000 literature seems to
point to scheduling a log backup job on a periodic basis. My workflow
isn't 24 hour consistant and even adjusting the interval during the
day isn't a good answer when the multiple databases on a server fill
their logs at different rates.

[Simon Hayes]

fp****@hotmail.com (Fred Prose) wrote in message news:<19**************************@posting.google. com>...

Has anyone explored a process whereby the Transaction Log would be
backup up based upon a defined threshold, ie. 75% full? All the
research against news group posts and SQL2000 literature seems to
point to scheduling a log backup job on a periodic basis. My workflow
isn't 24 hour consistant and even adjusting the interval during the
day isn't a good answer when the multiple databases on a server fill
their logs at different rates.

You could create an alert using Perfmon on the SQLServer:Databases
(Percent Log Used) counter, which fires at 75% and calls a batch file
or script to backup the log. Personally, I wouldn't do this because a)
it introduces unnecessary complexity, and b) it makes your backup
schedule completely unpredictable. If you don't know the backup
schedule, then you don't know what your recovery options are, which
makes it difficult to tell users and management anything about
possible data loss in the event of an outage.

Simon