# Durability

## What is the durability guaranteed by SingleStore?

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

See [CREATE DATABASE](https://docs.singlestore.com/db/v9.1/reference/sql-reference/data-definition-language-ddl/create-database.md) for more information.

## Can I configure SingleStore to be fully durable?

Yes, you can configure the durability through the `WITH {SYNC | ASYNC} DURABILITY` option in the [CREATE DATABASE](https://docs.singlestore.com/db/v9.1/reference/sql-reference/data-definition-language-ddl/create-database.md) and [RESTORE DATABASE](https://docs.singlestore.com/db/v9.1/reference/sql-reference/operational-commands/restore-database.md) commands.

## What isolation levels does SingleStore provide?

SingleStore 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” 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 SingleStore should take this into account.

***

Modified at: January 10, 2023

Source: [/db/v9.1/introduction/faqs/durability/](https://docs.singlestore.com/db/v9.1/introduction/faqs/durability/)

(An index of the documentation is available at /llms.txt)