Frequently Asked Questions
Frequently Asked Questions
Monitor the size of your Firebird vault database file
Posted by Sakari Heinonen (M-Files) on 25 April 2018 07:45 PM

When M-Files Vaults are in use, it is expected that their size on disk will gradually increase over time, regardless of what the database engine in use is. However, if Firebird SQL database is used, it is important to make sure that the vault size does not grow too large. When the Firebird vault reaches the size of 1GB, it's performance typically begins to degrade.


There is a registry setting M-Files Support can provide which allows using Firebird vaults of larger sizes that 1 GB if the M-Files server in use is a 64bit server. Take note, however, that even in this situation the vault's performance will usually begin to degrade even more before the size of the "metadata.fdb" database file reaches 3GB. These size limits vary quite a lot however, depending on the vault metadata structure and data content


In conclusion, is important to monitor the size of the metadata.fdb so that corrective steps - archiving data or preparing migration to MS SQL - can be initiated before the vault performance degrades extensively.


You can find more useful information and tips about monitoring and optimizing your M-Files Vault in this article: "Monitoring and Optimizing M-Files Performance"

Last edited: April 26th, 2018

M-Files Customer Support Team,

(2 vote(s))
This article was helpful
This article was not helpful

Help Desk Software by Kayako case