You are currently browsing legacy 2.0 version of documentation. Click here to switch to the newest 5.1 version.

We can help you with migration to the latest RavenDB

Contact Us Now
see on GitHub

Bundle: Quotas

The Quotas Bundle is helpful when you want to restrict the size of a database. By setting a hard limit and a soft margin, the bundle will make sure you never exceed the space you designate for it to use.

The database size is calculated based on the Esent or Munin data files (excluding the logs), plus the space the indexes are taking on disk.

Once the hard limit has reached, no additional documents will be let in the document store. However, indexing operations will resume normal operation even if that means the database size will go way over the hard limit. This is by design, to make sure the database is fully operational even when the hard limit has been met.

A soft limit is defined by the hard-limit minus the soft-limit margin, both are configurable. The first time the soft limit has been met, a warning will appear under Raven/WarningMessages with the Size Quota prefix.


To activate compression server-wide just add Quotas to Raven/ActiveBundles configuration in global configuration file or setup new database with compression bundle turned on using API or Studio.

How to create a database with quotas enabled using Studio can be found here.


Configure the following values by adding entries to your server configuration or database settings:

  • Raven/Quotas/Size/HardLimitInKB The hard limit after which we refuse any additional writes.
    Default: none

  • Raven/Quotas/Size/SoftMarginInKB The soft limit before which we will warn about the quota.
    Default: 1024

  • Raven/Quotas/Documents/HardLimit The hard limit after which we refuse any additional documents.
    Default: Int64.MaxValue

  • Raven/Quotas/Documents/SoftLimit The soft limit before which we will warn about the document limit quota.
    Default: Int64.MaxValue