Database Server Size

When enterprises become larger than 5000 workstations, it is hard to predict just how much CPU, RAM and disk space is required. In many of these enterprises, there is a wide variance in the quantity of menu items, employees, and content stored in the database. Additionally, the volume of checks coming in and the average size of those checks vary greatly; only general guidance can be provided.

Minimally, a Dual Quad Core CPU based server is recommended as a baseline for really large systems. Depending upon how much farther over 5000 workstations the system is going to go, consideration should be given up front to purchasing server hardware with the ability to add up to four CPUs, even if only two are purchased initially. The option to add CPUs can be exercised over time, as the load dictates.

When it comes to RAM, beginning with a minimum of 64 GB and having room to grow is prudent. At a relatively low cost, it is possible to procure servers today that are capable of expanding to hundreds of gigabytes. The amount of RAM consumed by the database grows as an enterprise grows. Careful monitoring needs to take place to ensure that the database servers do not become memory starved. Customers should be prepared to add RAM as the system grows over time.

Disk space usage grows as new properties are brought on line and more transactions start flowing in. Expect to see the transaction database grow and plateau as a result of each property coming on line. When a property comes online, there is new configuration data stored in the database. By default, check storage is disabled in Simphony. When the check storage option is enabled, up to 30 days worth of transaction data can be stored.

The Simphony reporting database also continues to grow based on the same rules that apply to smaller systems. For large reporting systems that keep multiple years of historical transactional data — which can grow up to 10-20TB of disk space — it may be advisable for customers to persist their Simphony data on a SAN, where additional resources can be added when needed. Installing the Simphony database files onto local hard drives limits the systems growth potential.