Reliable and Fast

SQLDatabase.Net uses transaction log file known as journal similar to sqlite, which can be created either on disk or in memory. SQL Database support rollback journal instead of simple logging. It provides atomic transaction which is a database operation in such a manner that either all of them occurs or nothing occurs, providing guarantee of atomicity prevents partial updates in database keeping database and data reliable.

A rollback journal is a temporary file used to implement commit and rollback capabilities, with rollback journal a transaction can be recovered if there is a crash such as power loss in the middle of transaction. SYSCMD command can define the path to use for journal file and can move it to a memory location which is default in portable class library. In desktop it is by default stored in same directory as database file. Each database file keeps seperate journal file providing simultaneous multi file commit without loss of information.

SQL Database also support transactions to speed up the insert, updates and deletes with atomic capabilities including commit and roll backs. Nested transactions or Named transactions are not supported, single thread capabilities keeps the database file consistent. The database integrity can be checked through system commands of integrity_check and quick_check.