Although you can create a separate procedure to dump the transaction log for each threshold, it is easier to create a single threshold procedure that is executed by all log segment thresholds. When the amount of free space on a segment falls below a threshold, Adaptive Server reads the systhresholds table in the affected database for the name of the associated stored procedure, which can be any of:
A remote procedure call to an Open Server
A procedure name qualified by a database name (for example, sybsystemprocs.dbo.sp_thresholdaction)
An unqualified procedure name
If the procedure name does not include a database qualifier, Adaptive Server looks in the database where the shortage of space occurred. If it cannot find the procedure there, and if the procedure name begins with the characters “sp_”, Adaptive Server looks for the procedure in the sybsystemprocs database and then in master database.
If Adaptive Server cannot find the threshold procedure, or cannot execute it, it prints a message in the error log.
