Consolidating multiple SQL Server systems onto
Dell PowerEdge R610 Servers using Microsoft’s Hyper-V
16
identify potential problems before you move to a Hyper-V based
solution. Second, you can use the information you gather to map
out your resource allocation needs, which you can then use to
configure your Hyper-V virtual machine memory and CPU settings.
Poor candidates for consolidation
Not every database is a good candidate for consolidation. Here, we
present examples of databases that possibly should remain on
dedicated servers.
Databases with critical performance requirements. If your
database has stringent performance requirements, it may be best
to leave it on a dedicated server. On a dedicated server, it is much
easier to find any bottlenecks that might occur. It is also much
simpler to address any problems when you need not worry about
disrupting other work on the same server. If you do decide to
proceed with consolidation, try to avoid consolidating two
performance-critical databases on the same server, because it may
not be possible to achieve acceptable performance for both of
them.
Databases with critical uptime requirements. Avoid
consolidating multiple highly critical databases on a single server.
To do so greatly magnifies the effect of a single server failure.
While high-availability measures such as clustering can help
mitigate this risk, it is often better not to have too many critical
resources vulnerable to a single point of failure.
Databases with critical security requirements. You may need
to isolate databases with highly sensitive data. You may be able to
handle some critical requirements by putting such a database in a
dedicated virtual machine, but you may decide that some
databases are sufficiently sensitive that you need to keep them on
dedicated physical servers.
Databases with specialized requirements. Some databases
may have requirements you cannot fulfill in the new environment,
such as applications that depend on highly specialized file layouts
or direct access to specific hardware.
Of course, you must also be sensitive to circumstances unique to
your organization. Contractual obligations, for example, might
require you to keep a given database on an isolated server.
Finally, you may want to avoid mixing contrasting types of work.
For example, the usage patterns and schema designs for Online
Analytical Processing (OLAP) and Online Transaction Processing
(OLTP) applications differ significantly. Each of these environments
employs different optimization techniques, and those techniques
may not mix well. If you consolidate your OLAP relational data
warehouse files physically alongside your OLTP database files, you
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comentários a estes Manuais