Durability

What is the durability guaranteed by SingleStoreDB?

SingleStoreDB provides several options to control the trade-offs between performance and durability. In its most durable state, SingleStoreDB will not lose any transactions that have been acknowledged.

See CREATE DATABASE for more information.

Can I configure SingleStoreDB to be fully durable?

Yes, you can configure the durability through the WITH {SYNC | ASYNC} DURABILITY option in the CREATE DATABASE and RESTORE DATABASE commands.

What isolation levels does SingleStoreDB provide?

SingleStoreDB provides the READ COMMITTED isolation level. This guarantees that no transaction will read any uncommitted data from another transaction. Furthermore, once a change is observed in one transaction, it will be visible to all transactions.

Unlike the REPEATABLE READ or SNAPSHOT isolation level, READ COMMITTED isolation level does not guarantee that a row will remain the same for every read query in a given transaction. Applications that use SingleStoreDB should take this into account.

Even though regular transactions use READ COMMITTED isolation level, backups created using the BACKUP command use SNAPSHOT isolation level.