Database Reference
In-Depth Information
Backup options
Business continuity and disaster recovery options
Some of the items listed will be dynamic within all tiers, meaning at any tier of the stack
a user can choose between two different operating system choices currently supported
by the organization. Other options will be toggled on or off within a tier. The reason for
the toggle is that a database does not have to be large to be mission critical to your
organization.
Table 5.1
provides an example of what a tiered model in your
organization might look like. It is important to remember that this is a starting point and
that the information in the table may look different in your organization. The memory in
the table is based on the recommendation of 6-8GB per vCPU. On the lower vCPU
limit, we use the 6GB calculation, and for the top vCPU limit, we use the 8GB
calculation.
Table 5.1
Sample Tiered Database Offering
Remember,
Table 5.1
is meant to be used as a starting point for your organization. Work
with the appropriate individuals within your organization to determine the correct
options and variables to place into your tiered database offering. In addition, if a
database is deployed in a specific tier and needs more than what was assigned, then the
self-service portal should allow the user to request additional resources and have this
request adhere to existing approval and change-control procedures.
By moving to a tiered database offering, commonly known as Database as a Service
(DaaS), you will achieve several benefits—the first being improved time to delivery.
