Enterprise Platform Database Server Requirements

The following table shows the requirements for an On-Premise Enterprise Platform installation running Cost Insight Report. Enterprise Platform installations that are not running Cost Insight Report (for example, running only Cost Insight Admin sync) have less stringent requirements. See the section following the table for details.

	Required	Recommended
Operating System 1	Oracle®: Any server-class OS supported by the database vendor. Microsoft SQL Server®: Any server-class OS supported by the database vendor. MySQL: Server-class Windows® or Linux®3 See “Software Requirements” below for supported Oracle, MySQL, and SQL Server versions. Note that a Cost Insight installation can include remote databases. You can have multiple database installations (for the operational and reporting databases, for example), and they do not need to be on a single machine. However, all servers must be on the same LAN.
RAM	6 GB	8 - 16 GB
Disk Space4	For demo installations: 5 GB For production installations, realistic numbers depend on the number of users, number and size of export sets2, and how long you expect to retain data. See Recommended column for conservative estimates that should be more than adequate for most installations. ==>	20 GB for up to 50 users 40 GB for 50 to 100 users 80 GB for 100 to 200 users

1 Enterprise Platform is tested against databases on Windows Server 2012 R2 x64 and 2016 x64. For demos and evaluations, it can run on Windows 8.1, and 10. Server-class OS is required for production environments, and any environment where production-like performance is needed (for example, performance/load testing environments, which should mimic production environments as much as is practicable). Server-class OS is recommended but not required for small deployments and other environments such as development, training, and demo systems.

Windows Server tests are performed with Standard Edition, which also validates Datacenter Edition. The following Server Editions are NOT validated: Standard-Core and Nano.

2 Number of scenarios, processes, operations, frequency of exports, etc.

3 When using MySQL on Linux, the MySQL installation must be case insensitive.

4 When the database is serving multiple applications, use the higher RAM and Disk Space recommendations. Note that disk recommendations include only aPriori usage, and do not take into account any DBA overhead or external factors such as back-up files.

Note: Each of the following Enterprise Platform components require a separate schema (or database, depending on the terminology for your DBMS), in addition to the aPriori “operational” database:

• JasperServer (“jasperserver”)

• Cost Insight Report (“reporting”)

• Quartz scheduler (“quartz”, shared by multiple components)

• Cost Insight Admin: Scenario and/or VPE Synchronization (“sync”, shared)

• Cost Insight Admin: LDAP Synchronization (“ldap_sync”)

See the Enterprise Platform Installation Guide for more information.