Database settings

To	Do this
Specify the maximum number of database files FileMaker Server can open at one time	For Maximum Number of Files to Host, enter a number up to 125. Note The memory requirements of FileMaker Server are directly related to the number of clients and open files. If you specify large values, you should also increase the amount of RAM reserved for the database cache.
Automatically host runtime solution files	In Registered Runtime Solutions, select Allow FileMaker Server to automatically host registered runtime solutions. If the runtime solutions do not have the .fmp12 filename extension, you must register their filename extensions in FileMaker Server. •To register a file type for a runtime solution, click Register and type the filename extension. •To remove a registered file type, select the file type in the File Type list and click Remove. If you host runtime database solutions created by FileMaker Pro Advanced, you can enable FileMaker Server to automatically open runtime solutions when FileMaker Server starts. Runtime solutions must be stored in one of the designated locations. See Database and backup folder settings.
Specify the RAM reserved for database cache	For RAM Reserved for Database Cache (MB), select the amount of memory. The maximum allowed database cache size is the smaller positive number of these two formulas: •the physical RAM size minus 1024 MB (1 GB) •90% of the physical RAM size Increasing the RAM reserved for the database cache can speed up overall performance for a correctly designed database, especially if your server hosts large files or a large number of clients or files.

Important The Database Server creates temporary files in a temporary directory on the master machine to cache data for hosted files. The Database Server creates one temporary file for each open hosted file, and automatically closes and deletes the temporary file when the associated hosted file is closed. Make sure there is enough free disk space on the master machine to store the temporary files. In most cases, the size of the temporary file is 10-20% of the size of the associated hosted file, but the actual percentage depends on the number of clients and server-side scripts and their activity level. The Database Server periodically checks the temporary file size and will shrink a temporary file if it grows too large compared to the amount of free disk space.