SQL Server 2014 hastens transaction processing. By Joab Jackson. Jun 5, 2013 7:05 am PDT. ... SQL Server 2012 then borrowed this columnar processing technique for its own use.

Distributed transactions are one of the more powerful and important functions within SQL Server. A distributed transaction is just like any other transaction within the SQL Server database, with a ...

SQL Server supports three recovery models: Simple, Bulk-Logged, and Full. The Simple model does not support transaction log backups and is suitable for scenarios where data loss is acceptable.

SQL Server keeps a buffer of all of the changes to data for performance reasons. It writes items to the transaction log immediately, but does not write changes to the data file immediately.

SQL Server 2014 will come with a new in-memory OLTP engine, one built with the company’s Heckaton set of technologies, ... Hekaton has been shown to cut transaction times by 50 times, ...

So I'm trying to figure out when I should be backing my transaction logs relative to my full/diffs. It seems like right after would be when I'd want to have the checkpoint happen, or does it ...

SQL Server, of course, keeps track of everything that affects data in a transaction log, which is periodically rolled over into backup files (at least, if you're being a conscientious DBA it is).