The transaction log for database 'database_name' is full due to 'XTP_CHECKPOINT' 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
First make sure that replication is not causing this, as stated in the connect item the &quot;log_wait_reuse_desc=XTP_CHECKPOINT does not necessarily mean that the XTP checkpoint worker is holding up log truncation.&quot; so start by running sp_repltrans and make certain that all data has been distributed.
Then there is this little snippet here:

&quot;it happens on a database, which has memory optimized file group, no matter there has memory optimized tables or not.
The current workaround is set the AutoGrown to be a fixed size. Or, changing the recovery mode to be Simple, and shrinking the log.&quot;

So if cleaning up replication does not work try the following:
checkpoint;
dbcc shrinkfile (Logfile, truncateonly)
alter database [database] modify file (filename = 'TRANSACTIONLOG', FILEGROWTH = 5MB)

It is not stated if this is for the log file or the database files but lets start by trying the log files and if not then try setting the database files to fixed growth: