Transaction logs

[ToddNKay]

Hello all,
We're having a problem with our transaction logs filling up. We're
constantly receiving an error: "syslogs is full". So we increase the size
of the transaction log and we're okay for a few thousand more transactions.
Is there any way of automatically clearing the logs so that we can keep the
log files at a specific size? This is going to be a major problem if the
log files just keep growing and growing...

Thanks in advance,

-Todd

[BPMargolin]

Todd:

The transaction logs will keep growing in size unless you do at least one of
the following:

1. Take regular backups of the database (look up in Books Online DUMP in SQL
Server 6.x, BACKUP in SQL Server 7.0). This is imperative if you need to be
able to recover the database in case of a server crash. When you backup the
database, you can truncate the transaction logs as they are now stored
elsewhere.

2. If the database is only in development mode, or if it can recreated from
an external source, or if it is not critical that transactions are lost, the
look up the "trunc. log on chkpt." option which will truncate the log for
you automatically (but will NOT allow you to recover from a server crash).

ToddNKay wrote in message ...

[Nazmul Siddiqui]

One of the options available for any database is truncate logs. Select it
and the logs will automatically be truncated every 60 seconds. You can get
to the menu offering the option through a right click on the database (SQL
Server 6.5). You may also manually truncate the logs. If you don't plan on
using these transaction logs then consider turning on the truncate logs
option on in the model database....Good luck