Database Reference
In-Depth Information
down with your stakeholders and set the correct expectations.
Baselining the Existing vSphere Infrastructure
It's important to understand the capabilities of your existing vSphere implementation
and what its expansion capacity is for additional workloads. It's so important that
Chapter 10
, “
How to Baseline Your Physical SQL Server System
,” focuses on how to
baseline your existing infrastructure to accurately determine what the current demand is
in terms of memory, disk, CPU, and network.
Will the existing spare capacity of the vSphere environment be able to service the needs
of a resource-intensive application such as a SQL Server database? You will hear this
many times as you read this topic. A common mistake people make is introducing a
production database onto an existing vSphere environment that was built for capacity,
not for performance, and then wonder why the database is not performing well. A
database is about acceptable performance first and foremost. Therefore, before you
move the database onto that existing infrastructure, make sure it's ready to get the job
done.
vSphere Environment: Things to Consider
There are a number of things you should consider as you baseline your existing vSphere
environment. All the information shown in
Table 4.2
can be gathered using ESXTOP.
This table is a subset of
Table 10.4
in
Chapter 10
.
The thresholds shown in
Table 4.2
are specific to when a vSphere environment contains a mission-critical SQL server
database.
