it can be defined simply as reduce the number of physical SQL servers, by migrating/moving different SQL databases running on different servers into one high performance server machine.
Early in the process of a consolidation project, you will create a profile to help identify which applications are good candidates for consolidation. Then you can identify the applications that fit this profile.
Some general traits that make an application a good candidate for consolidation are:
SQL server consolidation can be achieved mainly through one of the below strategies:
Each of these strategies has different advantages and disadvantages related to security and compliance requirements, high availability and disaster recovery requirements, resource management benefits, level of consolidation density, and manageability tradeoffs
Consolidation projects are typically started to achieve specific goals such as creating room for new servers or reducing operating expenditure. These goals can be broadly grouped into the following categories:
when choosing one of the consolidations strategies each of which has its cons and pros, in the below checklist im trying to list the main concerns to take care of , these concerns can be captured from different views as the following :
answering the below checklist will help you to decide the best strategy for your environment:
Share SQL service account for all applications (dbs)
Do you need to isolate system admins (e.g. sa)
Instance , VM
Do you need to isolate local windows admin account
Do you seek isolation on SQL binaries' and patching for each application DB ?
Full software & hardware resources isolation , Hard limits on CPU and memory usage set per application
Applications (DBs) can be moved to different HW without windows restart or downtime
Isolation of tempdb, one tempDb for all applications (dbs)
Isolation of server level objects (credentials, linked servers, msdb, SQL Server Agent jobs, and so on)
Best performance when same hardware is provided
Reduces number of physical servers to maintain
Reduces number of Windows installations to maintain
Reduces number of SQL Server instances to maintain
Are you seeking reduced management overhead and licensing cost
Number of applications
Host system CPU utilization
Baseline (old hardware)
Table : sample Density results based on throughput (higher is better) and response time (lower is better) across options
next blog , how to use MAP tool to assess your environment readiness for SQL consolidation :
Good post Issa :)
Very nice article.Good information
Precise & nice information shared in this article, specially the information shared via tables.
Nice article..it's help me lot