The on-premises database server is experiencing high memory and CPU utilization over the course of a month. The current on-premises infrastructure is at capacity with no ability to scale up. The Chief

Increasing CPU on the database server is a capital expenditure and contradicts the requirement for no capital expenditure, and the current on-premises infrastructure is already at capacity.

Allocating more RAM to the database server is a capital expenditure and contradicts the requirement for no capital expenditure, and the current on-premises infrastructure is already at capacity.

Increasing storage on the database server does not address high CPU and memory utilization and typically involves capital expenditure.

Migrating to a Database-as-a-Service (DBaaS) solution directly addresses resource exhaustion by providing elastic scaling capabilities for CPU and memory, eliminating the need for upfront hardware purchases. This approach shifts the expenditure from a capital expenditure (CapEx) model to an operational expenditure (OpEx) model, aligning with the requirement for no capital expenditure while resolving scalability issues.

Migrating the database to a new on-premises server would still incur capital expenditure for new hardware and would not provide the flexible, elastic scalability of a cloud service.