Truncating the Transaction Log

Sybase IQ records in the transaction log the information necessary to recover from a system failure. Although the information logged is small for each committed transaction, the transaction log continues to grow in size. In systems with a high number of transactions that change data, over a period of time the log can grow to be very large.

When to truncate the log is really up to the DBA responsible for supporting the Sybase IQ systems, and depends on the growth profile of the log file and the operational procedures at the site.

The following table shows methods for truncating Sybase IQ transaction logs.

Truncating transaction logs

If your database is …

Use this method …

For details, see …

Stopped

“The –m switch, which causes the transaction log to be truncated after each checkpoint for all databases

“Truncating the transaction log of a stopped database”

Running

The dbbackup command line utility with the -xo switch or the -r switch

Utility Guide > Database Administration Utilities > Backup utility (dbbackup)

Related concepts
Message Log
Related tasks
Truncating the Transaction Log Of a Stopped Database