THE INFORMATION IN THIS ARTICLE APPLIES TO:
- EFT Server (All Versions)
How much storage space does the ARM database require?
Database capacity planning can be very simple or very complex depending on the needs and size of the organization. Space requirements for transactions depend on estimated EFT Server activity, number of users, installed modules, number of Event Rules defined/enabled, and many other factors.
3GB minimum hard drive space is recommended for the initial database size.
Space requirements for transactions depend on estimated EFT Server activity, number of users, installed modules, Event Rules, and so on. A general estimate is 3MB to 5 MB per 1000 files uploaded.
A good database maintenance plan is important to keeping space requirements to a minimum (aging/archiving/warehousing/truncating old data).
For better database performance, follow the standard SQL/Oracle tuning guidelines in their user documentation.
If you are using SQL Server 2008 Developer and Enterprise editions for your EFT Server database, refer to the MSDN article Creating Compressed Tables and Indexes.
Also refer to the following GlobalSCAPE Knowledge Base articles:
We used the following procedure to determine the general estimate of 3 MB to 5MB per 1000 files uploaded:
Executed the built-in stored procedure sp_spaceused and recorded the initial database size. (The “reserved” column indicates how much data is in the database.)
Ran 20000 file uploads via scripted CuteFTP.
Executed the built-in stored procedure sp_spaceused and recorded the final database size.
Subtracted the initial size from the final size and divided the result by the number of transactions.
Optionally provide private feedback to help us improve this article...
Thank you for your feedback!