If your sp_thresholdaction procedure includes a dump transaction command, Adaptive Server dumps the log to the devices named in the procedure. dump transaction truncates the transaction log by removing all pages from the beginning of the log, up to the page just before the page that contains an uncommitted transaction record.
When there is enough log space, suspended transactions are awakened. If you abort transactions rather than suspending them, users must resubmit them.
Generally, dumping to a disk is not recommended, especially to a disk that is on the same machine or the same disk controller as the database disk. However, since threshold-initiated dumps can take place at any time, you may want to dump to disk and then copy the resulting files to offline media. (You will have to copy the files back to the disk to reload them.)
Your choice will depend on:
Whether you have a dedicated dump device online, loaded and ready to receive dumped data
Whether you have operators available to mount tape volumes during the times when your database is available
The size of your transaction log
Your transaction rate
Your regular schedule for dumping databases and transaction logs
Available disk space
Other site-specific dump resources and constraints
