Dangers of Using with truncate_only and with no_log

The with truncate_only and with no_log parameters allow you to truncate a log that has become disastrously short of free space.

Neither option provides a means to recover transactions that have committed since the last routine dump.

Warning!   Run dump database at the earliest opportunity to ensure that your data can be recovered.

This example truncates the transaction log for mydb and then dumps the database:

dump transaction mydb
    with no_log
dump database mydb to ...
Parent topic: Truncating a Log that Has No Free Space