A memory-optimized table can make transaction-log maintenance behave differently from ordinary tables. A common mistake is assuming that automatic checkpoints will arrive often enough to permit log truncation. section 12.7
Watch for these operational signals:
- XTP_CHECKPOINT waits can indicate problems flushing persistent memory-optimized table data streams to disk. section 12.7
- On smaller systems, automatic checkpoints may wait for 1.5 GB of transaction-log activity, allowing log truncation to remain stalled. section 12.7
- Older SQL Server 2014 and 2016 deployments may require the latest service pack and cumulative update because checkpoint bugs existed. section 12.7
A safer backup routine
If log truncation does not occur on a small system, schedule a manual CHECKPOINT before the transaction-log backup. Add that step to SQL Agent or coordinate it with the enterprise backup policy. section 12.7
