Posted on 1998-07-02
The transaction log in our sybase 11 production database fills up fast
although its size is fairly large, resulting is a half-minute pause at
an unpredictable time while the log is dumped.
Under normal operation, one process deletes a large set of rows from a
table and then inserts another set. Other processs read these rows.
I suspect the inserts and deletes are logged and cause the problem.
There is no transaction involved and we do not want to recover that
particular table if the database goes down.
Truncate table (which does not log) is not allowed in our production databases.
Any other suggestions for getting around this problem?