When dump transaction frees sufficient log space, suspended processes automatically awaken and complete. If writetext or select into has resulted in unlogged changes to the database since the last backup, you can run dump tran with truncate_only, which runs even in a situation with nonlogged-writes. If log space is so critical that dump tran with truncate_only fails, you can run dump tran with no_log. However, use dump tran with no_log for emergencies only, and run only as a last resort.
After the transaction dump completes, and transactions have successfully been freed from the log suspend state, the system administrator or database owner can dump the database.
If this does not free enough space to awaken the suspended processes, increase the size of the transaction log using the log on option of alter database.
As an alternative to killing the command, you can use lct_admin("abort", spid), which might be preferable to killing the connection because you may want to maintain the connection. See the Reference Manual: Building Blocks.
If you have system administrator privileges, use sp_who to determine which processes are in a log suspend status, then use the kill command to waken the sleeping process.
