01
Buy for the workload, not the database name
Bring a workload profile: database engine and version, active data size, peak memory use, concurrent queries, write volume and growth. Include indexes, transaction logs, temporary space and maintenance jobs. A small business database and a reporting warehouse can need very different machines even when they use the same software.
Identify the constraint you are trying to change. If an existing system waits on storage or a remote application, buying more cores is not evidence that the problem will disappear. Use your own query mix and a representative dataset to establish acceptance criteria for the new host.
02
Compare three different allocations
These candidates offer different memory and disk allocations; they are not ranked by transactions per second. Listed raw capacity is not usable database space after your chosen redundancy.
- Xeon E-2388G: 64 GB of listed ECC memory and 2 TB raw NVMe capacity. A smaller candidate when the measured workload fits comfortably.
- EPYC 7443P: 256 GB of listed ECC memory and 7.68 TB raw NVMe capacity. Compare it when memory or data growth excludes the smaller configuration.
- EPYC 7513: four NVMe devices and 15.36 TB raw capacity. Consider it when the intended disk layout needs more devices, then confirm the actual configuration.
03
Agree what protects the data
Ask for the drive model and endurance where sustained writes matter. The catalogue does not publish measured IOPS, commit latency or a database benchmark. Specify the disk layout and recovery requirement instead of assuming that NVMe or ECC makes a complete resilience plan.
A single rental is one physical host, not a managed database cluster. Replication, failover, database-aware backups and restore testing remain your responsibility unless separately agreed. Confirm any network separation required between database nodes; a public port or a second machine does not include a private replication network.
04
Price the complete deployment and migration
Compare the rental alongside database licensing, backup storage and any quoted options. Check software licensing against the exact processor allocation. Select the operating system and confirm its release, disk layout and access method before installation; renting hardware does not include database administration.
Choose a region against the application's network needs and confirm the model's delivery window. Preserve the existing database until the new host passes your checks and a restore has been demonstrated. A queued installation request is not a completed migration or a reason to remove the old copy.
Direct answers
Questions before you order
Do you promise a query rate or database latency?
No measured database performance is published. Set acceptance criteria using your engine, schema, query mix and dataset; a hardware specification alone cannot establish the result.
Is database management or automatic failover included?
No. This is dedicated hardware rental. Confirm any separately agreed assistance, and plan administration, replication, backups and recovery before moving production data.