What is the reason for the SQL Server transaction log to be filled up

Source: Internet
Author: User

The SQL Server transaction log may be filled, which blocks subsequent database operations, including update, DELETE, INSERT, and checkpoint.

Full transaction log fills can cause 1105 errors:

Can ' t allocate space for object syslogs in database dbname because

The logsegment is full. If you are ran out of spaces in syslogs, dump

The transaction log. Otherwise use ALTER DATABASE or

Sp_extendsegment to increase the size of the segment.

This behavior may occur in any database, including master and tempdb. Some unpredictable factors may consume log space. For example:

A large transaction, especially as a batch data update, insert, or delete.

A transaction that has not been committed.

The required bandwidth is too large for a checkpoint handler to intercept.

Truncation exceeded threshold

The results of interaction between the various conditions mentioned above.

The token transaction used for the publication is not read by the Log reader

Related Article

E-Commerce Solutions

Leverage the same tools powering the Alibaba Ecosystem

Learn more >

Apsara Conference 2019

The Rise of Data Intelligence, September 25th - 27th, Hangzhou, China

Learn more >

Alibaba Cloud Free Trial

Learn and experience the power of Alibaba Cloud with a free trial worth $300-1200 USD

Learn more >

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.