The transaction log for database ‘[database_name]’ is full due to ‘XTP_CHECKPOINT’‏ 

When using In-Memory OLTP in SQL Server 2014, under certain conditions you might get the below error message: The transaction log for database ‘[database_name]’ is full due to ‘XTP_CHECKPOINT’‏ 



One symptom due to the above issue, is that the transaction log of a memory-optimized table, might continue to grow, without being able to truncate or shrink it.


How to Fix the Issue

This was fixed in Cumulative Update 3 for SQL Server 2014 SP1 (and later)

More information about the fix can be found here.


Strengthen your SQL Server Administration Skills – Enroll to our Online Course!

Check our online course on Udemy titled “Essential SQL Server Administration Tips
(special limited-time discount included in link).

Via the course, you will learn essential hands-on SQL Server Administration tips on SQL Server maintenance, security, performance, integration, error handling and more. Many live demonstrations and downloadable resources included!

Essential SQL Server Administration Tips - Online Course with Live Demonstrations and Hands-on Guides
(Lifetime Access/ Live Demos / Downloadable Resources and more!)

Learn More


Featured Online Courses


Read Also

Feel free to check our other relevant articles on SQL Server troubleshooting:


Featured Database Productivity Tools

Snippets Generator: Create and modify T-SQL snippets for use in SQL Management Studio, fast, easy and efficiently.

Snippets Generator - SQL Snippets Creation Tool

Learn more


Dynamic SQL Generator: Convert static T-SQL code to dynamic and vice versa, easily and fast.

Dynamic SQL Generator: Easily convert static SQL Server T-SQL scripts to dynamic and vice versa.

Learn more


Subscribe to our newsletter and stay up to date!

Check out our latest software releases!

Check out Artemakis’s eBooks!


Rate this article: 1 Star2 Stars3 Stars4 Stars5 Stars (2 votes, average: 5.00 out of 5)


Reference: (

© SQLNetHub