Raul Gonzalez looks at how transaction logging works with memory-optimized tables:
Now we need double the rows, because for each row we’ve said it’s been deleted, we have to tell SQL Server that was not actually deleted (COMPENSATION due to ROLLBACK) in case of recovery (crash recovery or backup recovery). That’s so bad.
But not everything is lost yet
let’s check how the In-Memory engine deal with this problem
Memory-optimized tables are pretty neat.