Consider the following recommendations for your database server:
-
Because the database server regulates the overall solution, size it appropriately. It can be scaled up, but not out.
-
More processing cores are useful, but be aware of how your database management system processor core is priced.
-
Consider x64 to benefit from a larger buffer memory cache at Standard Edition pricing.
-
Input/output (I/O) speed is important to prevent disrupting the write caching of the transaction log.
-
Both storage area networks (SAN) and direct-attach storage (DAS) methods are capable of meeting functional and performance requirements, so one is not recommended over the other.
-
For the best database performance, the general recommendation for input/output completions is 10ms or less for the transaction log and temporary spaces, and 20ms for the table and index files.
-
Ensure network latency is as close to zero as possible for server components, processing stations, and OnBase Clients that are connected to the database server. A near-zero network latency means that transactions are virtually instantaneous.
-
Tune the database management system for online transaction processing work to accommodate larger workloads.
-
Use high availability technologies, such as clustering, mirroring, and log shipping, which are provided by database management system vendors. Multiple network ports can be used as well.
For the latest information about database server guidelines and requirements, visit the Hyland Community and refer to the Database Guides.