The transaction log for database 'database_name' is full due to 'XTP_CHECKPOINT'
29
votes
4
answers
30481
views
I have a question about
XTP_CHECKPOINT
.
I'm using SQL Server 2014. I have a database that is in SIMPLE recovery model mode. It is also being replicated.
There are no open transactions. I've run DBCC OPENTRAN
and it returns:
> "No active open transactions."
But I keep getting this message whenever I try to create or drop a table or delete data:
(I've replaced my actual database name with the word database_name
)
>"The transaction log for database 'database_name' is full due to 'XTP_CHECKPOINT'"
Does anyone know why this might be happening, and, more importantly, how can I make it stop?
And yes, the database really is in SIMPLE recovery model mode. i.e. The transaction log should truncate automatically.
Incidentally, another database that I have in full recovery mode did the same thing, started returning the same error:
>The transaction log for database 'database_name' is full due to 'XTP_CHECKPOINT'
I tried to change the log growth settings to unlimited growth, but it wouldn't let me, returning the same error.
I can reproduce the problem without any XTP stuff at all, except for just the filegroup. Here's how: http://pastebin.com/jWSiEU9U
Asked by user3469285
(671 rep)
Feb 23, 2015, 05:25 PM
Last activity: Sep 6, 2023, 07:39 PM
Last activity: Sep 6, 2023, 07:39 PM