The SQL Server transaction log may be filled, which prevents subsequent database operations, including update, DELETE, INSERT, and checkpoint.
Filling the transaction log will result in a 1105 error:
Can ' t allocate space for object syslogs in database dbname because
The logsegment is full.
If you ran out of space in syslogs, dump
The transaction log.
Otherwise use ALTER DATABASE or
Sp_extendsegment to increase the size of the segment.
This behavior can occur in any database, including master and tempdb. Some unpredictable factors may consume log space.
For example:
A large transaction, especially like bulk data update, insert, or delete.
A non-committed transaction.
The required bandwidth is too large for the checkpoint handler to truncate.
Threshold exceeded when truncated
The results of the interaction between the various conditions mentioned above.
The marked transaction for publishing was not read by the Log reader.
http://www.bkjia.com/PHPjc/631171.html www.bkjia.com true http://www.bkjia.com/PHPjc/631171.html techarticle The SQL Server transaction log may be filled, which prevents subsequent database operations, including update, DELETE, INSERT, and checkpoint. A full transaction log can cause a 1105 error: Can ' t allo ...
