Although database files can be configured to automatically grow as a database gets larger, this configuration can create a significant overhead and affect performance. This is especially true if the server has to allocate space frequently. In addition, physical fragmentation can occur if auto-growth options are not properly set. It is recommended that you pre-size these files so that auto-growth is not required.
When sizing a database, size the database files and logs as accurately as possible to their "final" size. At a minimum, size the files to support two years of growth. OnBase currently uses 14 different files (filegroups/tablespaces) to allow for flexible and effective distribution of data.
For sizing formulas for each database space, see Database Layout. If necessary, Hyland Software, Inc. can assist with sizing estimation for each file. As a failsafe, the auto-growth option can remain enabled, but increments should be set to 10% or 100MB, depending on the rate of growth.