RESERVE_SIZE= number{ k | m | g }

0 (no reserve size).

The value you supply can be any value from 0 to your maximum database size. Use k, m, or g to specify units of kilobytes, megabytes, or gigabytes, respectively. If you do not specify a unit, bytes are assumed by default.

You should run the database with test data and observe the database size and choose a reserve size that suits your UltraLite deployment.

If the RESERVE_SIZE value is smaller than the database size, UltraLite ignores the parameter.

Reserving file system space can improve performance slightly because it may:

Because an UltraLite database consists of data and metadata, the database size grows only when required (when the application updates the database).

• UltraLite connection strings and parameters
• UltraLite CACHE_SIZE connection parameter
• UltraLite page_size creation parameter
• UltraLite for C/C++: Connecting to an UltraLite database
• ULDatabaseManager.OpenConnection method [UltraLite C++]
• UltraLite for embedded SQL: Connect to an UltraLite database
• UltraLite for M-Business Anywhere: Connect to an UltraLite database
• DatabaseManager.openConnection method [UltraLite for M-Business Anywhere]
• UltraLite.NET: Connecting to an UltraLite database
• ULConnection.Open method [UltraLite.NET]

The following connection string fragment sets the reserve size to 128 KB so the system reserves that much system space for the database upon startup.

"RESERVE_SIZE=128K"