Database infrastructure without the tax
Database infrastructure is where sizing mistakes cost the most, because the software licensing often prices by core. A host with more cores than the workload needs isn't just wasted hardware; on per-core licensing it's a recurring tax that can exceed the server's price every year.
The right shape is usually fewer, faster cores, memory sized to keep the working set hot, and storage with a latency budget in fractions of a millisecond. Overcommitting CPU on a latency-sensitive database host is how you buy hardware and still get blamed for slow queries.
What actually determines the answer
| Factor | Why it matters |
|---|---|
| Licensing model | Per-core licensing changes the optimal host: fewer, faster cores beat more, slower ones. Run the licensing math before the hardware math. |
| Working set size | Memory that holds the hot data is the cheapest performance you can buy. Size RAM to the working set, not the database size. |
| Latency budget | Transactional workloads care about storage latency at the 99th percentile, not average throughput. All-NVMe, short path, no contention. |
| Consolidation discipline | Databases can share a host at 2:1 or 3:1 vCPU ratios with care. Mixing them into a 4:1 general cluster is how noisy neighbors happen. |
The paths, with their trade-offs
Dedicated database hosts
When licensing is per-core or the workload is latency-critical.
Trade-off: Host count rises, but licensed cores and blame both drop. Usually the cheapest option in total.
Configured BOM
R770 - 30 VM virtualization host
- CPU 2× Intel Xeon 6 processor, 32 cores each
- Memory 8× 32 GB DDR5 RDIMM (256 GB total)
- Storage 4× 1.92 TB NVMe read-intensive SSD
- Network Dual-port 25 GbE adapter
- Support 4-year ProSupport Plus, next business day
Shared array for consolidated databases
When several databases can share storage with a real latency budget.
Trade-off: One array serving many databases needs headroom held in reserve, or the busiest one taxes the rest.
Configured BOM
PowerStore 1200T - virtualization array
- Appliance PowerStore 1200T, dual-node 2U base enclosure
- Media 12× 3.84 TB NVMe SSD
- Connectivity 25 GbE iSCSI / NVMe-TCP
- Support 4-year ProSupport Plus, next business day
Run your own numbers first: VM sizing calculator →
What deployment involves
Typical scope: host and storage build, migration in coordination with your DBA team, and a before-and-after latency baseline so the improvement is measured, not asserted.