DATABASE CONSOLIDATION WITH SQL SERVER 2008
Justin LangfordPrincipal Consultantjustincoeocom
AGENDA
Business and technical drivers Why consolidate Type of consolidation
Planning and considerations Key considerations Designing SQL instance and common configurations
Guiding principles Consolidation process Migration Techniques
Potential issues and solutions Shared components Using WSRM or Resource Governor
DATABASE SPRAWL - THE PROBLEM
SQL Server is prolific in most mid-large organisationsWide selection of versions and editionsMany bespoke non-standard configurationsServers deployed ldquoper-applicationrdquoMany servers under-utilisedLicensing and maintenance costs
CONSOLIDATION ndash WHATrsquoS THAT
Data database instance consolidationHost same databases with fewer serversShare resources across multiple environmentsBetter resource utilisationReduced support costs
BIZSQLSERVER2SERVER1
BIZSQLSQL2SQL1
SQL CONSOLIDATION
BIZSRVSERVER1
BIZSQLSQL1
SERVER1
BIZSQLSQL1
Today
Database
consolidation
SQL Instance
consolidation
SERVER VIRTUALISATION
Windows 2008 Server
Virtual Machine Manager
Virtual Machine
Virtual Machine
Virtual Machine
Virtual Machine
VIRTUALISATION VS CONSOLIDATION
Virtualisation Consolidation
Same
Goal reduce physical servers Goal to reduce physical serversSavings on power licensing maintenance
Savings on power licensing maintenance
Performance concerns Performance concerns
Different
Same number of OS Fewer OSSame databases instance More databases instanceSame number of instances Fewer instancesNo Windows SQL Upgrade Can upgrade Windows and SQLldquoBlack-boxrdquo approach Lots of engineering test effortAdditional layer of technology More mixed workloadHardware abstraction Tight hardware integration
Consolidation Virtualisation
HOW NOW
Affordable performanceMulti-core CPUs64-bit MemoryDisk IO ndash Solid State Disks
Core 1Core 2
Core 3Core 4
CONSOLIDATION DIMENSIONS
Management amp Administrative Processes
StandardsIndependent
Fewer
Physical Locations
Several
O
ne
Mul
tiple
SQ
L In
stan
ces
per
Win
dow
s
Win
dow
s Per
Ser
ver
O
ne
Man
y - V
irtua
lisati
on
DBs p
er
SQL I
nsta
nce
Som
e
Hundr
eds
Some DataDatabaseDuplication
Lot
Current amp ldquoTo Berdquo position along each dimension
CONSOLIDATION CONSIDERDATIONS
Resource requirements of databases Processor memory disk IO and network TempDB usage
Dependencies outside user database Third party support Instance-wide settings security model Replication Log Shipping Database Mirroring
Collation and sort order
BUSINESS DRIVERS
Why consolidate
Reduced costs Standardisation Better server utilisation Space electricity cooling License costsBetter control of IT Processes Consistent operations BaR DR Maintenance
Improved Business Integration
Consolidation activities can reduce costs by 10 percent to 25 percent or more in some casesGartner March 2008
TECHNICAL BENEFITS
Multi-InstanceFlexibility to based on Service Level Agreements (SLA) requirements Performance Backup Recovery Security Change control Operational Upgrade
Multiple development environments on single serverSupport larger workloads on a single serverSeveral trade-offs considerations (more later)
TECHNICAL BENEFITS
Single InstanceAvoid of fixed overhead of multiple instance Fixed server memory configuration Single set of EXEs DLLs etc
Some components are always shared anywayDynamic memory for single instance serverLess administrative workSeveral trade-offs and considerations (more later)
TECHNICAL BENEFITS
Multi-Windows Instance (Virtualisation)
MoreProvides OS IsolationToo many instances decrease value of high end servers
LessReduces scale-up capabilityCan increase risk (single OS point of failure)
HIGH-LEVEL PLANNING
CONSOLIDATION SUCCESS FACTORS
Consolidation
Strategy
People
Process
Technology
HIGH LEVEL PLANNING
Strategy
Motivation for consolidation and end goalsMeasure quantify benefitsEstablish Guiding Principles
People
Potential change in the ownership (DBA Custodianship) of databull Technically Database Ownership (DBO) can be retained
Ongoing support and change managementbull System Administration role change
HIGH LEVEL PLANNING
ProcessAdministrative Operational Performance MonitoringTuning BackupRestore Capacity PlanningMigration and rollback planning
TechnologyCPU memory management IO subsystemWorkload isolationConsolidation ndash name conflicts objects security logins
Management FocusCritical to success
CONSOLIDATION ROADMAP
SQL 2000 2005 amp older
instances
SQL 2008 (2005) Instances
Much More Challenging
One at a time or
en-masse
One at a timeCurrent Environment
ldquoTo Berdquo Environment
bull Monitor behavior
bull Stabilise
Staging Environment
Test amp Production Consolidated
SQL 2008
GUIDING PRINCIPLES
Evaluate Customise and Adopt
Start by consolidating non-mission critical workloadUpgrade to SQL 2008 before consolidating Consolidate similar workloads into single SQL Server instanceAvoid bug fixes during consolidationMaintain transparent user experience Drive standardisation (configuration and operations)
PLANNING DESIGN amp IMPLEMENTATION
PLAN DESIGN IMPLEMENT
Stage 1 ndash Envision1 Current Environment Assessment
Discovery Audit Business Requirements SLA RPO RTO Workload profile transaction volumes processor disk memory SQL Server feature usage Linked servers Extended SP
2 Identify Target Environment amp Develop Consolidation Principles First cut ldquoTo Berdquo environment Discuss gather feedback revise target environment Review financial justification - RoI Develop Consolidation Guiding Principles
PLAN DESIGN IMPLEMENT
Stage 2 ndash Plan amp Design
3 Design lsquoFuturersquo Consolidated Infrastructure Develop design Blueprint Design Review
4 Service User amp Data Migration Planning Migration approach Deployment planning Sequencing of Applications Users Data Design develop migration scripts
PLAN DESIGN IMPLEMENT
Stage 3 ndash Implement
5 Commission consolidated environment for test Test parallel to production Migrate test database
bull Test Migration processbull Load capacity testing highly recommended
Gain confidence in platform and workload profile Isolate identify fix issues
PLAN DESIGN IMPLEMENT
Stage 4 ndash Deploy amp Stabilise
6 Build amp deploy Production Consolidated SQL Service Consolidatemigrate incrementally
bull Capture baselinebull Add incrementally (ONE at a time)bull Stabilisebull Measure again
Transparent User Experience
7 Measure new Service Compare with lsquooldrsquo Retire old servers
TECHNICAL CONSIDERATIONS
MULTI-INSTANCE SERVERS
Min Max server memoryCPU affinity maskWindows System Resource Manager (WSRM)Failover cluster Possible owners Preferred owners AntiAffinityClassName
SERVER1
BIZSQLSQL1
PLANNING MULTI DATABASES
Resource Governor Min max CPU Min max Memory
Un-managed Worker threads TempDB Plan cache
SERVER1
SQL1
VIRTUALISATION DESIGN
Proper hardware sizing criticalGood storage configuration is critical Use fixed or pass-thru disks (avoid dynamic disks) Avoid thin-provisioning Tune storage configuration
Limitations 4 virtual processor per guest 64 cores in host 64 GB memory in host
x64 benefits are significantAvoid over-committing CPU or memoryStart with single VPU
Recommendations
VIRTUALISATION WITH HIGH AVAILABILITY
Virtual machine failoverHigh Availability regardless of Windows or SQL edition
Live Migration with Hyper-V Uses Failover clustering Requires Win 2008 R2 Single host failover
VIRTUALISATION FOR SITE RESILIENCE
Using virtualisation to provide site resilienceSite-to-site disaster recovery
INTERESTING READS
SQL Server Consolidation Whitepaperhttpwwwmicrosoftcomsqlserver2008enuswhite-papersaspx
SQL Server Virtualisation Whitepaperhttpdownloadmicrosoftcomdownloadd94d948f981-926e-40fa-a026-5bfcf076d9b9SQL2008inHyperV2008docx
Microsoft Assessment and Planning Toolkit httpwwwmicrosoftcomdownloadsdetailsaspxFamilyID=67240b76-3148-4e49-943d-4d9ea7f77730ampdisplaylang=en
Windows System Resource Manager (WSRM)httptechnetmicrosoftcomen-uslibrarycc771218(WS10)aspx
SUMMARY
Plan Design Deliver ConsolidationConstruct Guiding Principles
Identify good candidates for consolidationProviding workload
isolationAn approach to consolidating an estate
AGENDA
Business and technical drivers Why consolidate Type of consolidation
Planning and considerations Key considerations Designing SQL instance and common configurations
Guiding principles Consolidation process Migration Techniques
Potential issues and solutions Shared components Using WSRM or Resource Governor
DATABASE SPRAWL - THE PROBLEM
SQL Server is prolific in most mid-large organisationsWide selection of versions and editionsMany bespoke non-standard configurationsServers deployed ldquoper-applicationrdquoMany servers under-utilisedLicensing and maintenance costs
CONSOLIDATION ndash WHATrsquoS THAT
Data database instance consolidationHost same databases with fewer serversShare resources across multiple environmentsBetter resource utilisationReduced support costs
BIZSQLSERVER2SERVER1
BIZSQLSQL2SQL1
SQL CONSOLIDATION
BIZSRVSERVER1
BIZSQLSQL1
SERVER1
BIZSQLSQL1
Today
Database
consolidation
SQL Instance
consolidation
SERVER VIRTUALISATION
Windows 2008 Server
Virtual Machine Manager
Virtual Machine
Virtual Machine
Virtual Machine
Virtual Machine
VIRTUALISATION VS CONSOLIDATION
Virtualisation Consolidation
Same
Goal reduce physical servers Goal to reduce physical serversSavings on power licensing maintenance
Savings on power licensing maintenance
Performance concerns Performance concerns
Different
Same number of OS Fewer OSSame databases instance More databases instanceSame number of instances Fewer instancesNo Windows SQL Upgrade Can upgrade Windows and SQLldquoBlack-boxrdquo approach Lots of engineering test effortAdditional layer of technology More mixed workloadHardware abstraction Tight hardware integration
Consolidation Virtualisation
HOW NOW
Affordable performanceMulti-core CPUs64-bit MemoryDisk IO ndash Solid State Disks
Core 1Core 2
Core 3Core 4
CONSOLIDATION DIMENSIONS
Management amp Administrative Processes
StandardsIndependent
Fewer
Physical Locations
Several
O
ne
Mul
tiple
SQ
L In
stan
ces
per
Win
dow
s
Win
dow
s Per
Ser
ver
O
ne
Man
y - V
irtua
lisati
on
DBs p
er
SQL I
nsta
nce
Som
e
Hundr
eds
Some DataDatabaseDuplication
Lot
Current amp ldquoTo Berdquo position along each dimension
CONSOLIDATION CONSIDERDATIONS
Resource requirements of databases Processor memory disk IO and network TempDB usage
Dependencies outside user database Third party support Instance-wide settings security model Replication Log Shipping Database Mirroring
Collation and sort order
BUSINESS DRIVERS
Why consolidate
Reduced costs Standardisation Better server utilisation Space electricity cooling License costsBetter control of IT Processes Consistent operations BaR DR Maintenance
Improved Business Integration
Consolidation activities can reduce costs by 10 percent to 25 percent or more in some casesGartner March 2008
TECHNICAL BENEFITS
Multi-InstanceFlexibility to based on Service Level Agreements (SLA) requirements Performance Backup Recovery Security Change control Operational Upgrade
Multiple development environments on single serverSupport larger workloads on a single serverSeveral trade-offs considerations (more later)
TECHNICAL BENEFITS
Single InstanceAvoid of fixed overhead of multiple instance Fixed server memory configuration Single set of EXEs DLLs etc
Some components are always shared anywayDynamic memory for single instance serverLess administrative workSeveral trade-offs and considerations (more later)
TECHNICAL BENEFITS
Multi-Windows Instance (Virtualisation)
MoreProvides OS IsolationToo many instances decrease value of high end servers
LessReduces scale-up capabilityCan increase risk (single OS point of failure)
HIGH-LEVEL PLANNING
CONSOLIDATION SUCCESS FACTORS
Consolidation
Strategy
People
Process
Technology
HIGH LEVEL PLANNING
Strategy
Motivation for consolidation and end goalsMeasure quantify benefitsEstablish Guiding Principles
People
Potential change in the ownership (DBA Custodianship) of databull Technically Database Ownership (DBO) can be retained
Ongoing support and change managementbull System Administration role change
HIGH LEVEL PLANNING
ProcessAdministrative Operational Performance MonitoringTuning BackupRestore Capacity PlanningMigration and rollback planning
TechnologyCPU memory management IO subsystemWorkload isolationConsolidation ndash name conflicts objects security logins
Management FocusCritical to success
CONSOLIDATION ROADMAP
SQL 2000 2005 amp older
instances
SQL 2008 (2005) Instances
Much More Challenging
One at a time or
en-masse
One at a timeCurrent Environment
ldquoTo Berdquo Environment
bull Monitor behavior
bull Stabilise
Staging Environment
Test amp Production Consolidated
SQL 2008
GUIDING PRINCIPLES
Evaluate Customise and Adopt
Start by consolidating non-mission critical workloadUpgrade to SQL 2008 before consolidating Consolidate similar workloads into single SQL Server instanceAvoid bug fixes during consolidationMaintain transparent user experience Drive standardisation (configuration and operations)
PLANNING DESIGN amp IMPLEMENTATION
PLAN DESIGN IMPLEMENT
Stage 1 ndash Envision1 Current Environment Assessment
Discovery Audit Business Requirements SLA RPO RTO Workload profile transaction volumes processor disk memory SQL Server feature usage Linked servers Extended SP
2 Identify Target Environment amp Develop Consolidation Principles First cut ldquoTo Berdquo environment Discuss gather feedback revise target environment Review financial justification - RoI Develop Consolidation Guiding Principles
PLAN DESIGN IMPLEMENT
Stage 2 ndash Plan amp Design
3 Design lsquoFuturersquo Consolidated Infrastructure Develop design Blueprint Design Review
4 Service User amp Data Migration Planning Migration approach Deployment planning Sequencing of Applications Users Data Design develop migration scripts
PLAN DESIGN IMPLEMENT
Stage 3 ndash Implement
5 Commission consolidated environment for test Test parallel to production Migrate test database
bull Test Migration processbull Load capacity testing highly recommended
Gain confidence in platform and workload profile Isolate identify fix issues
PLAN DESIGN IMPLEMENT
Stage 4 ndash Deploy amp Stabilise
6 Build amp deploy Production Consolidated SQL Service Consolidatemigrate incrementally
bull Capture baselinebull Add incrementally (ONE at a time)bull Stabilisebull Measure again
Transparent User Experience
7 Measure new Service Compare with lsquooldrsquo Retire old servers
TECHNICAL CONSIDERATIONS
MULTI-INSTANCE SERVERS
Min Max server memoryCPU affinity maskWindows System Resource Manager (WSRM)Failover cluster Possible owners Preferred owners AntiAffinityClassName
SERVER1
BIZSQLSQL1
PLANNING MULTI DATABASES
Resource Governor Min max CPU Min max Memory
Un-managed Worker threads TempDB Plan cache
SERVER1
SQL1
VIRTUALISATION DESIGN
Proper hardware sizing criticalGood storage configuration is critical Use fixed or pass-thru disks (avoid dynamic disks) Avoid thin-provisioning Tune storage configuration
Limitations 4 virtual processor per guest 64 cores in host 64 GB memory in host
x64 benefits are significantAvoid over-committing CPU or memoryStart with single VPU
Recommendations
VIRTUALISATION WITH HIGH AVAILABILITY
Virtual machine failoverHigh Availability regardless of Windows or SQL edition
Live Migration with Hyper-V Uses Failover clustering Requires Win 2008 R2 Single host failover
VIRTUALISATION FOR SITE RESILIENCE
Using virtualisation to provide site resilienceSite-to-site disaster recovery
INTERESTING READS
SQL Server Consolidation Whitepaperhttpwwwmicrosoftcomsqlserver2008enuswhite-papersaspx
SQL Server Virtualisation Whitepaperhttpdownloadmicrosoftcomdownloadd94d948f981-926e-40fa-a026-5bfcf076d9b9SQL2008inHyperV2008docx
Microsoft Assessment and Planning Toolkit httpwwwmicrosoftcomdownloadsdetailsaspxFamilyID=67240b76-3148-4e49-943d-4d9ea7f77730ampdisplaylang=en
Windows System Resource Manager (WSRM)httptechnetmicrosoftcomen-uslibrarycc771218(WS10)aspx
SUMMARY
Plan Design Deliver ConsolidationConstruct Guiding Principles
Identify good candidates for consolidationProviding workload
isolationAn approach to consolidating an estate
DATABASE SPRAWL - THE PROBLEM
SQL Server is prolific in most mid-large organisationsWide selection of versions and editionsMany bespoke non-standard configurationsServers deployed ldquoper-applicationrdquoMany servers under-utilisedLicensing and maintenance costs
CONSOLIDATION ndash WHATrsquoS THAT
Data database instance consolidationHost same databases with fewer serversShare resources across multiple environmentsBetter resource utilisationReduced support costs
BIZSQLSERVER2SERVER1
BIZSQLSQL2SQL1
SQL CONSOLIDATION
BIZSRVSERVER1
BIZSQLSQL1
SERVER1
BIZSQLSQL1
Today
Database
consolidation
SQL Instance
consolidation
SERVER VIRTUALISATION
Windows 2008 Server
Virtual Machine Manager
Virtual Machine
Virtual Machine
Virtual Machine
Virtual Machine
VIRTUALISATION VS CONSOLIDATION
Virtualisation Consolidation
Same
Goal reduce physical servers Goal to reduce physical serversSavings on power licensing maintenance
Savings on power licensing maintenance
Performance concerns Performance concerns
Different
Same number of OS Fewer OSSame databases instance More databases instanceSame number of instances Fewer instancesNo Windows SQL Upgrade Can upgrade Windows and SQLldquoBlack-boxrdquo approach Lots of engineering test effortAdditional layer of technology More mixed workloadHardware abstraction Tight hardware integration
Consolidation Virtualisation
HOW NOW
Affordable performanceMulti-core CPUs64-bit MemoryDisk IO ndash Solid State Disks
Core 1Core 2
Core 3Core 4
CONSOLIDATION DIMENSIONS
Management amp Administrative Processes
StandardsIndependent
Fewer
Physical Locations
Several
O
ne
Mul
tiple
SQ
L In
stan
ces
per
Win
dow
s
Win
dow
s Per
Ser
ver
O
ne
Man
y - V
irtua
lisati
on
DBs p
er
SQL I
nsta
nce
Som
e
Hundr
eds
Some DataDatabaseDuplication
Lot
Current amp ldquoTo Berdquo position along each dimension
CONSOLIDATION CONSIDERDATIONS
Resource requirements of databases Processor memory disk IO and network TempDB usage
Dependencies outside user database Third party support Instance-wide settings security model Replication Log Shipping Database Mirroring
Collation and sort order
BUSINESS DRIVERS
Why consolidate
Reduced costs Standardisation Better server utilisation Space electricity cooling License costsBetter control of IT Processes Consistent operations BaR DR Maintenance
Improved Business Integration
Consolidation activities can reduce costs by 10 percent to 25 percent or more in some casesGartner March 2008
TECHNICAL BENEFITS
Multi-InstanceFlexibility to based on Service Level Agreements (SLA) requirements Performance Backup Recovery Security Change control Operational Upgrade
Multiple development environments on single serverSupport larger workloads on a single serverSeveral trade-offs considerations (more later)
TECHNICAL BENEFITS
Single InstanceAvoid of fixed overhead of multiple instance Fixed server memory configuration Single set of EXEs DLLs etc
Some components are always shared anywayDynamic memory for single instance serverLess administrative workSeveral trade-offs and considerations (more later)
TECHNICAL BENEFITS
Multi-Windows Instance (Virtualisation)
MoreProvides OS IsolationToo many instances decrease value of high end servers
LessReduces scale-up capabilityCan increase risk (single OS point of failure)
HIGH-LEVEL PLANNING
CONSOLIDATION SUCCESS FACTORS
Consolidation
Strategy
People
Process
Technology
HIGH LEVEL PLANNING
Strategy
Motivation for consolidation and end goalsMeasure quantify benefitsEstablish Guiding Principles
People
Potential change in the ownership (DBA Custodianship) of databull Technically Database Ownership (DBO) can be retained
Ongoing support and change managementbull System Administration role change
HIGH LEVEL PLANNING
ProcessAdministrative Operational Performance MonitoringTuning BackupRestore Capacity PlanningMigration and rollback planning
TechnologyCPU memory management IO subsystemWorkload isolationConsolidation ndash name conflicts objects security logins
Management FocusCritical to success
CONSOLIDATION ROADMAP
SQL 2000 2005 amp older
instances
SQL 2008 (2005) Instances
Much More Challenging
One at a time or
en-masse
One at a timeCurrent Environment
ldquoTo Berdquo Environment
bull Monitor behavior
bull Stabilise
Staging Environment
Test amp Production Consolidated
SQL 2008
GUIDING PRINCIPLES
Evaluate Customise and Adopt
Start by consolidating non-mission critical workloadUpgrade to SQL 2008 before consolidating Consolidate similar workloads into single SQL Server instanceAvoid bug fixes during consolidationMaintain transparent user experience Drive standardisation (configuration and operations)
PLANNING DESIGN amp IMPLEMENTATION
PLAN DESIGN IMPLEMENT
Stage 1 ndash Envision1 Current Environment Assessment
Discovery Audit Business Requirements SLA RPO RTO Workload profile transaction volumes processor disk memory SQL Server feature usage Linked servers Extended SP
2 Identify Target Environment amp Develop Consolidation Principles First cut ldquoTo Berdquo environment Discuss gather feedback revise target environment Review financial justification - RoI Develop Consolidation Guiding Principles
PLAN DESIGN IMPLEMENT
Stage 2 ndash Plan amp Design
3 Design lsquoFuturersquo Consolidated Infrastructure Develop design Blueprint Design Review
4 Service User amp Data Migration Planning Migration approach Deployment planning Sequencing of Applications Users Data Design develop migration scripts
PLAN DESIGN IMPLEMENT
Stage 3 ndash Implement
5 Commission consolidated environment for test Test parallel to production Migrate test database
bull Test Migration processbull Load capacity testing highly recommended
Gain confidence in platform and workload profile Isolate identify fix issues
PLAN DESIGN IMPLEMENT
Stage 4 ndash Deploy amp Stabilise
6 Build amp deploy Production Consolidated SQL Service Consolidatemigrate incrementally
bull Capture baselinebull Add incrementally (ONE at a time)bull Stabilisebull Measure again
Transparent User Experience
7 Measure new Service Compare with lsquooldrsquo Retire old servers
TECHNICAL CONSIDERATIONS
MULTI-INSTANCE SERVERS
Min Max server memoryCPU affinity maskWindows System Resource Manager (WSRM)Failover cluster Possible owners Preferred owners AntiAffinityClassName
SERVER1
BIZSQLSQL1
PLANNING MULTI DATABASES
Resource Governor Min max CPU Min max Memory
Un-managed Worker threads TempDB Plan cache
SERVER1
SQL1
VIRTUALISATION DESIGN
Proper hardware sizing criticalGood storage configuration is critical Use fixed or pass-thru disks (avoid dynamic disks) Avoid thin-provisioning Tune storage configuration
Limitations 4 virtual processor per guest 64 cores in host 64 GB memory in host
x64 benefits are significantAvoid over-committing CPU or memoryStart with single VPU
Recommendations
VIRTUALISATION WITH HIGH AVAILABILITY
Virtual machine failoverHigh Availability regardless of Windows or SQL edition
Live Migration with Hyper-V Uses Failover clustering Requires Win 2008 R2 Single host failover
VIRTUALISATION FOR SITE RESILIENCE
Using virtualisation to provide site resilienceSite-to-site disaster recovery
INTERESTING READS
SQL Server Consolidation Whitepaperhttpwwwmicrosoftcomsqlserver2008enuswhite-papersaspx
SQL Server Virtualisation Whitepaperhttpdownloadmicrosoftcomdownloadd94d948f981-926e-40fa-a026-5bfcf076d9b9SQL2008inHyperV2008docx
Microsoft Assessment and Planning Toolkit httpwwwmicrosoftcomdownloadsdetailsaspxFamilyID=67240b76-3148-4e49-943d-4d9ea7f77730ampdisplaylang=en
Windows System Resource Manager (WSRM)httptechnetmicrosoftcomen-uslibrarycc771218(WS10)aspx
SUMMARY
Plan Design Deliver ConsolidationConstruct Guiding Principles
Identify good candidates for consolidationProviding workload
isolationAn approach to consolidating an estate
CONSOLIDATION ndash WHATrsquoS THAT
Data database instance consolidationHost same databases with fewer serversShare resources across multiple environmentsBetter resource utilisationReduced support costs
BIZSQLSERVER2SERVER1
BIZSQLSQL2SQL1
SQL CONSOLIDATION
BIZSRVSERVER1
BIZSQLSQL1
SERVER1
BIZSQLSQL1
Today
Database
consolidation
SQL Instance
consolidation
SERVER VIRTUALISATION
Windows 2008 Server
Virtual Machine Manager
Virtual Machine
Virtual Machine
Virtual Machine
Virtual Machine
VIRTUALISATION VS CONSOLIDATION
Virtualisation Consolidation
Same
Goal reduce physical servers Goal to reduce physical serversSavings on power licensing maintenance
Savings on power licensing maintenance
Performance concerns Performance concerns
Different
Same number of OS Fewer OSSame databases instance More databases instanceSame number of instances Fewer instancesNo Windows SQL Upgrade Can upgrade Windows and SQLldquoBlack-boxrdquo approach Lots of engineering test effortAdditional layer of technology More mixed workloadHardware abstraction Tight hardware integration
Consolidation Virtualisation
HOW NOW
Affordable performanceMulti-core CPUs64-bit MemoryDisk IO ndash Solid State Disks
Core 1Core 2
Core 3Core 4
CONSOLIDATION DIMENSIONS
Management amp Administrative Processes
StandardsIndependent
Fewer
Physical Locations
Several
O
ne
Mul
tiple
SQ
L In
stan
ces
per
Win
dow
s
Win
dow
s Per
Ser
ver
O
ne
Man
y - V
irtua
lisati
on
DBs p
er
SQL I
nsta
nce
Som
e
Hundr
eds
Some DataDatabaseDuplication
Lot
Current amp ldquoTo Berdquo position along each dimension
CONSOLIDATION CONSIDERDATIONS
Resource requirements of databases Processor memory disk IO and network TempDB usage
Dependencies outside user database Third party support Instance-wide settings security model Replication Log Shipping Database Mirroring
Collation and sort order
BUSINESS DRIVERS
Why consolidate
Reduced costs Standardisation Better server utilisation Space electricity cooling License costsBetter control of IT Processes Consistent operations BaR DR Maintenance
Improved Business Integration
Consolidation activities can reduce costs by 10 percent to 25 percent or more in some casesGartner March 2008
TECHNICAL BENEFITS
Multi-InstanceFlexibility to based on Service Level Agreements (SLA) requirements Performance Backup Recovery Security Change control Operational Upgrade
Multiple development environments on single serverSupport larger workloads on a single serverSeveral trade-offs considerations (more later)
TECHNICAL BENEFITS
Single InstanceAvoid of fixed overhead of multiple instance Fixed server memory configuration Single set of EXEs DLLs etc
Some components are always shared anywayDynamic memory for single instance serverLess administrative workSeveral trade-offs and considerations (more later)
TECHNICAL BENEFITS
Multi-Windows Instance (Virtualisation)
MoreProvides OS IsolationToo many instances decrease value of high end servers
LessReduces scale-up capabilityCan increase risk (single OS point of failure)
HIGH-LEVEL PLANNING
CONSOLIDATION SUCCESS FACTORS
Consolidation
Strategy
People
Process
Technology
HIGH LEVEL PLANNING
Strategy
Motivation for consolidation and end goalsMeasure quantify benefitsEstablish Guiding Principles
People
Potential change in the ownership (DBA Custodianship) of databull Technically Database Ownership (DBO) can be retained
Ongoing support and change managementbull System Administration role change
HIGH LEVEL PLANNING
ProcessAdministrative Operational Performance MonitoringTuning BackupRestore Capacity PlanningMigration and rollback planning
TechnologyCPU memory management IO subsystemWorkload isolationConsolidation ndash name conflicts objects security logins
Management FocusCritical to success
CONSOLIDATION ROADMAP
SQL 2000 2005 amp older
instances
SQL 2008 (2005) Instances
Much More Challenging
One at a time or
en-masse
One at a timeCurrent Environment
ldquoTo Berdquo Environment
bull Monitor behavior
bull Stabilise
Staging Environment
Test amp Production Consolidated
SQL 2008
GUIDING PRINCIPLES
Evaluate Customise and Adopt
Start by consolidating non-mission critical workloadUpgrade to SQL 2008 before consolidating Consolidate similar workloads into single SQL Server instanceAvoid bug fixes during consolidationMaintain transparent user experience Drive standardisation (configuration and operations)
PLANNING DESIGN amp IMPLEMENTATION
PLAN DESIGN IMPLEMENT
Stage 1 ndash Envision1 Current Environment Assessment
Discovery Audit Business Requirements SLA RPO RTO Workload profile transaction volumes processor disk memory SQL Server feature usage Linked servers Extended SP
2 Identify Target Environment amp Develop Consolidation Principles First cut ldquoTo Berdquo environment Discuss gather feedback revise target environment Review financial justification - RoI Develop Consolidation Guiding Principles
PLAN DESIGN IMPLEMENT
Stage 2 ndash Plan amp Design
3 Design lsquoFuturersquo Consolidated Infrastructure Develop design Blueprint Design Review
4 Service User amp Data Migration Planning Migration approach Deployment planning Sequencing of Applications Users Data Design develop migration scripts
PLAN DESIGN IMPLEMENT
Stage 3 ndash Implement
5 Commission consolidated environment for test Test parallel to production Migrate test database
bull Test Migration processbull Load capacity testing highly recommended
Gain confidence in platform and workload profile Isolate identify fix issues
PLAN DESIGN IMPLEMENT
Stage 4 ndash Deploy amp Stabilise
6 Build amp deploy Production Consolidated SQL Service Consolidatemigrate incrementally
bull Capture baselinebull Add incrementally (ONE at a time)bull Stabilisebull Measure again
Transparent User Experience
7 Measure new Service Compare with lsquooldrsquo Retire old servers
TECHNICAL CONSIDERATIONS
MULTI-INSTANCE SERVERS
Min Max server memoryCPU affinity maskWindows System Resource Manager (WSRM)Failover cluster Possible owners Preferred owners AntiAffinityClassName
SERVER1
BIZSQLSQL1
PLANNING MULTI DATABASES
Resource Governor Min max CPU Min max Memory
Un-managed Worker threads TempDB Plan cache
SERVER1
SQL1
VIRTUALISATION DESIGN
Proper hardware sizing criticalGood storage configuration is critical Use fixed or pass-thru disks (avoid dynamic disks) Avoid thin-provisioning Tune storage configuration
Limitations 4 virtual processor per guest 64 cores in host 64 GB memory in host
x64 benefits are significantAvoid over-committing CPU or memoryStart with single VPU
Recommendations
VIRTUALISATION WITH HIGH AVAILABILITY
Virtual machine failoverHigh Availability regardless of Windows or SQL edition
Live Migration with Hyper-V Uses Failover clustering Requires Win 2008 R2 Single host failover
VIRTUALISATION FOR SITE RESILIENCE
Using virtualisation to provide site resilienceSite-to-site disaster recovery
INTERESTING READS
SQL Server Consolidation Whitepaperhttpwwwmicrosoftcomsqlserver2008enuswhite-papersaspx
SQL Server Virtualisation Whitepaperhttpdownloadmicrosoftcomdownloadd94d948f981-926e-40fa-a026-5bfcf076d9b9SQL2008inHyperV2008docx
Microsoft Assessment and Planning Toolkit httpwwwmicrosoftcomdownloadsdetailsaspxFamilyID=67240b76-3148-4e49-943d-4d9ea7f77730ampdisplaylang=en
Windows System Resource Manager (WSRM)httptechnetmicrosoftcomen-uslibrarycc771218(WS10)aspx
SUMMARY
Plan Design Deliver ConsolidationConstruct Guiding Principles
Identify good candidates for consolidationProviding workload
isolationAn approach to consolidating an estate
BIZSQLSERVER2SERVER1
BIZSQLSQL2SQL1
SQL CONSOLIDATION
BIZSRVSERVER1
BIZSQLSQL1
SERVER1
BIZSQLSQL1
Today
Database
consolidation
SQL Instance
consolidation
SERVER VIRTUALISATION
Windows 2008 Server
Virtual Machine Manager
Virtual Machine
Virtual Machine
Virtual Machine
Virtual Machine
VIRTUALISATION VS CONSOLIDATION
Virtualisation Consolidation
Same
Goal reduce physical servers Goal to reduce physical serversSavings on power licensing maintenance
Savings on power licensing maintenance
Performance concerns Performance concerns
Different
Same number of OS Fewer OSSame databases instance More databases instanceSame number of instances Fewer instancesNo Windows SQL Upgrade Can upgrade Windows and SQLldquoBlack-boxrdquo approach Lots of engineering test effortAdditional layer of technology More mixed workloadHardware abstraction Tight hardware integration
Consolidation Virtualisation
HOW NOW
Affordable performanceMulti-core CPUs64-bit MemoryDisk IO ndash Solid State Disks
Core 1Core 2
Core 3Core 4
CONSOLIDATION DIMENSIONS
Management amp Administrative Processes
StandardsIndependent
Fewer
Physical Locations
Several
O
ne
Mul
tiple
SQ
L In
stan
ces
per
Win
dow
s
Win
dow
s Per
Ser
ver
O
ne
Man
y - V
irtua
lisati
on
DBs p
er
SQL I
nsta
nce
Som
e
Hundr
eds
Some DataDatabaseDuplication
Lot
Current amp ldquoTo Berdquo position along each dimension
CONSOLIDATION CONSIDERDATIONS
Resource requirements of databases Processor memory disk IO and network TempDB usage
Dependencies outside user database Third party support Instance-wide settings security model Replication Log Shipping Database Mirroring
Collation and sort order
BUSINESS DRIVERS
Why consolidate
Reduced costs Standardisation Better server utilisation Space electricity cooling License costsBetter control of IT Processes Consistent operations BaR DR Maintenance
Improved Business Integration
Consolidation activities can reduce costs by 10 percent to 25 percent or more in some casesGartner March 2008
TECHNICAL BENEFITS
Multi-InstanceFlexibility to based on Service Level Agreements (SLA) requirements Performance Backup Recovery Security Change control Operational Upgrade
Multiple development environments on single serverSupport larger workloads on a single serverSeveral trade-offs considerations (more later)
TECHNICAL BENEFITS
Single InstanceAvoid of fixed overhead of multiple instance Fixed server memory configuration Single set of EXEs DLLs etc
Some components are always shared anywayDynamic memory for single instance serverLess administrative workSeveral trade-offs and considerations (more later)
TECHNICAL BENEFITS
Multi-Windows Instance (Virtualisation)
MoreProvides OS IsolationToo many instances decrease value of high end servers
LessReduces scale-up capabilityCan increase risk (single OS point of failure)
HIGH-LEVEL PLANNING
CONSOLIDATION SUCCESS FACTORS
Consolidation
Strategy
People
Process
Technology
HIGH LEVEL PLANNING
Strategy
Motivation for consolidation and end goalsMeasure quantify benefitsEstablish Guiding Principles
People
Potential change in the ownership (DBA Custodianship) of databull Technically Database Ownership (DBO) can be retained
Ongoing support and change managementbull System Administration role change
HIGH LEVEL PLANNING
ProcessAdministrative Operational Performance MonitoringTuning BackupRestore Capacity PlanningMigration and rollback planning
TechnologyCPU memory management IO subsystemWorkload isolationConsolidation ndash name conflicts objects security logins
Management FocusCritical to success
CONSOLIDATION ROADMAP
SQL 2000 2005 amp older
instances
SQL 2008 (2005) Instances
Much More Challenging
One at a time or
en-masse
One at a timeCurrent Environment
ldquoTo Berdquo Environment
bull Monitor behavior
bull Stabilise
Staging Environment
Test amp Production Consolidated
SQL 2008
GUIDING PRINCIPLES
Evaluate Customise and Adopt
Start by consolidating non-mission critical workloadUpgrade to SQL 2008 before consolidating Consolidate similar workloads into single SQL Server instanceAvoid bug fixes during consolidationMaintain transparent user experience Drive standardisation (configuration and operations)
PLANNING DESIGN amp IMPLEMENTATION
PLAN DESIGN IMPLEMENT
Stage 1 ndash Envision1 Current Environment Assessment
Discovery Audit Business Requirements SLA RPO RTO Workload profile transaction volumes processor disk memory SQL Server feature usage Linked servers Extended SP
2 Identify Target Environment amp Develop Consolidation Principles First cut ldquoTo Berdquo environment Discuss gather feedback revise target environment Review financial justification - RoI Develop Consolidation Guiding Principles
PLAN DESIGN IMPLEMENT
Stage 2 ndash Plan amp Design
3 Design lsquoFuturersquo Consolidated Infrastructure Develop design Blueprint Design Review
4 Service User amp Data Migration Planning Migration approach Deployment planning Sequencing of Applications Users Data Design develop migration scripts
PLAN DESIGN IMPLEMENT
Stage 3 ndash Implement
5 Commission consolidated environment for test Test parallel to production Migrate test database
bull Test Migration processbull Load capacity testing highly recommended
Gain confidence in platform and workload profile Isolate identify fix issues
PLAN DESIGN IMPLEMENT
Stage 4 ndash Deploy amp Stabilise
6 Build amp deploy Production Consolidated SQL Service Consolidatemigrate incrementally
bull Capture baselinebull Add incrementally (ONE at a time)bull Stabilisebull Measure again
Transparent User Experience
7 Measure new Service Compare with lsquooldrsquo Retire old servers
TECHNICAL CONSIDERATIONS
MULTI-INSTANCE SERVERS
Min Max server memoryCPU affinity maskWindows System Resource Manager (WSRM)Failover cluster Possible owners Preferred owners AntiAffinityClassName
SERVER1
BIZSQLSQL1
PLANNING MULTI DATABASES
Resource Governor Min max CPU Min max Memory
Un-managed Worker threads TempDB Plan cache
SERVER1
SQL1
VIRTUALISATION DESIGN
Proper hardware sizing criticalGood storage configuration is critical Use fixed or pass-thru disks (avoid dynamic disks) Avoid thin-provisioning Tune storage configuration
Limitations 4 virtual processor per guest 64 cores in host 64 GB memory in host
x64 benefits are significantAvoid over-committing CPU or memoryStart with single VPU
Recommendations
VIRTUALISATION WITH HIGH AVAILABILITY
Virtual machine failoverHigh Availability regardless of Windows or SQL edition
Live Migration with Hyper-V Uses Failover clustering Requires Win 2008 R2 Single host failover
VIRTUALISATION FOR SITE RESILIENCE
Using virtualisation to provide site resilienceSite-to-site disaster recovery
INTERESTING READS
SQL Server Consolidation Whitepaperhttpwwwmicrosoftcomsqlserver2008enuswhite-papersaspx
SQL Server Virtualisation Whitepaperhttpdownloadmicrosoftcomdownloadd94d948f981-926e-40fa-a026-5bfcf076d9b9SQL2008inHyperV2008docx
Microsoft Assessment and Planning Toolkit httpwwwmicrosoftcomdownloadsdetailsaspxFamilyID=67240b76-3148-4e49-943d-4d9ea7f77730ampdisplaylang=en
Windows System Resource Manager (WSRM)httptechnetmicrosoftcomen-uslibrarycc771218(WS10)aspx
SUMMARY
Plan Design Deliver ConsolidationConstruct Guiding Principles
Identify good candidates for consolidationProviding workload
isolationAn approach to consolidating an estate
SERVER VIRTUALISATION
Windows 2008 Server
Virtual Machine Manager
Virtual Machine
Virtual Machine
Virtual Machine
Virtual Machine
VIRTUALISATION VS CONSOLIDATION
Virtualisation Consolidation
Same
Goal reduce physical servers Goal to reduce physical serversSavings on power licensing maintenance
Savings on power licensing maintenance
Performance concerns Performance concerns
Different
Same number of OS Fewer OSSame databases instance More databases instanceSame number of instances Fewer instancesNo Windows SQL Upgrade Can upgrade Windows and SQLldquoBlack-boxrdquo approach Lots of engineering test effortAdditional layer of technology More mixed workloadHardware abstraction Tight hardware integration
Consolidation Virtualisation
HOW NOW
Affordable performanceMulti-core CPUs64-bit MemoryDisk IO ndash Solid State Disks
Core 1Core 2
Core 3Core 4
CONSOLIDATION DIMENSIONS
Management amp Administrative Processes
StandardsIndependent
Fewer
Physical Locations
Several
O
ne
Mul
tiple
SQ
L In
stan
ces
per
Win
dow
s
Win
dow
s Per
Ser
ver
O
ne
Man
y - V
irtua
lisati
on
DBs p
er
SQL I
nsta
nce
Som
e
Hundr
eds
Some DataDatabaseDuplication
Lot
Current amp ldquoTo Berdquo position along each dimension
CONSOLIDATION CONSIDERDATIONS
Resource requirements of databases Processor memory disk IO and network TempDB usage
Dependencies outside user database Third party support Instance-wide settings security model Replication Log Shipping Database Mirroring
Collation and sort order
BUSINESS DRIVERS
Why consolidate
Reduced costs Standardisation Better server utilisation Space electricity cooling License costsBetter control of IT Processes Consistent operations BaR DR Maintenance
Improved Business Integration
Consolidation activities can reduce costs by 10 percent to 25 percent or more in some casesGartner March 2008
TECHNICAL BENEFITS
Multi-InstanceFlexibility to based on Service Level Agreements (SLA) requirements Performance Backup Recovery Security Change control Operational Upgrade
Multiple development environments on single serverSupport larger workloads on a single serverSeveral trade-offs considerations (more later)
TECHNICAL BENEFITS
Single InstanceAvoid of fixed overhead of multiple instance Fixed server memory configuration Single set of EXEs DLLs etc
Some components are always shared anywayDynamic memory for single instance serverLess administrative workSeveral trade-offs and considerations (more later)
TECHNICAL BENEFITS
Multi-Windows Instance (Virtualisation)
MoreProvides OS IsolationToo many instances decrease value of high end servers
LessReduces scale-up capabilityCan increase risk (single OS point of failure)
HIGH-LEVEL PLANNING
CONSOLIDATION SUCCESS FACTORS
Consolidation
Strategy
People
Process
Technology
HIGH LEVEL PLANNING
Strategy
Motivation for consolidation and end goalsMeasure quantify benefitsEstablish Guiding Principles
People
Potential change in the ownership (DBA Custodianship) of databull Technically Database Ownership (DBO) can be retained
Ongoing support and change managementbull System Administration role change
HIGH LEVEL PLANNING
ProcessAdministrative Operational Performance MonitoringTuning BackupRestore Capacity PlanningMigration and rollback planning
TechnologyCPU memory management IO subsystemWorkload isolationConsolidation ndash name conflicts objects security logins
Management FocusCritical to success
CONSOLIDATION ROADMAP
SQL 2000 2005 amp older
instances
SQL 2008 (2005) Instances
Much More Challenging
One at a time or
en-masse
One at a timeCurrent Environment
ldquoTo Berdquo Environment
bull Monitor behavior
bull Stabilise
Staging Environment
Test amp Production Consolidated
SQL 2008
GUIDING PRINCIPLES
Evaluate Customise and Adopt
Start by consolidating non-mission critical workloadUpgrade to SQL 2008 before consolidating Consolidate similar workloads into single SQL Server instanceAvoid bug fixes during consolidationMaintain transparent user experience Drive standardisation (configuration and operations)
PLANNING DESIGN amp IMPLEMENTATION
PLAN DESIGN IMPLEMENT
Stage 1 ndash Envision1 Current Environment Assessment
Discovery Audit Business Requirements SLA RPO RTO Workload profile transaction volumes processor disk memory SQL Server feature usage Linked servers Extended SP
2 Identify Target Environment amp Develop Consolidation Principles First cut ldquoTo Berdquo environment Discuss gather feedback revise target environment Review financial justification - RoI Develop Consolidation Guiding Principles
PLAN DESIGN IMPLEMENT
Stage 2 ndash Plan amp Design
3 Design lsquoFuturersquo Consolidated Infrastructure Develop design Blueprint Design Review
4 Service User amp Data Migration Planning Migration approach Deployment planning Sequencing of Applications Users Data Design develop migration scripts
PLAN DESIGN IMPLEMENT
Stage 3 ndash Implement
5 Commission consolidated environment for test Test parallel to production Migrate test database
bull Test Migration processbull Load capacity testing highly recommended
Gain confidence in platform and workload profile Isolate identify fix issues
PLAN DESIGN IMPLEMENT
Stage 4 ndash Deploy amp Stabilise
6 Build amp deploy Production Consolidated SQL Service Consolidatemigrate incrementally
bull Capture baselinebull Add incrementally (ONE at a time)bull Stabilisebull Measure again
Transparent User Experience
7 Measure new Service Compare with lsquooldrsquo Retire old servers
TECHNICAL CONSIDERATIONS
MULTI-INSTANCE SERVERS
Min Max server memoryCPU affinity maskWindows System Resource Manager (WSRM)Failover cluster Possible owners Preferred owners AntiAffinityClassName
SERVER1
BIZSQLSQL1
PLANNING MULTI DATABASES
Resource Governor Min max CPU Min max Memory
Un-managed Worker threads TempDB Plan cache
SERVER1
SQL1
VIRTUALISATION DESIGN
Proper hardware sizing criticalGood storage configuration is critical Use fixed or pass-thru disks (avoid dynamic disks) Avoid thin-provisioning Tune storage configuration
Limitations 4 virtual processor per guest 64 cores in host 64 GB memory in host
x64 benefits are significantAvoid over-committing CPU or memoryStart with single VPU
Recommendations
VIRTUALISATION WITH HIGH AVAILABILITY
Virtual machine failoverHigh Availability regardless of Windows or SQL edition
Live Migration with Hyper-V Uses Failover clustering Requires Win 2008 R2 Single host failover
VIRTUALISATION FOR SITE RESILIENCE
Using virtualisation to provide site resilienceSite-to-site disaster recovery
INTERESTING READS
SQL Server Consolidation Whitepaperhttpwwwmicrosoftcomsqlserver2008enuswhite-papersaspx
SQL Server Virtualisation Whitepaperhttpdownloadmicrosoftcomdownloadd94d948f981-926e-40fa-a026-5bfcf076d9b9SQL2008inHyperV2008docx
Microsoft Assessment and Planning Toolkit httpwwwmicrosoftcomdownloadsdetailsaspxFamilyID=67240b76-3148-4e49-943d-4d9ea7f77730ampdisplaylang=en
Windows System Resource Manager (WSRM)httptechnetmicrosoftcomen-uslibrarycc771218(WS10)aspx
SUMMARY
Plan Design Deliver ConsolidationConstruct Guiding Principles
Identify good candidates for consolidationProviding workload
isolationAn approach to consolidating an estate
VIRTUALISATION VS CONSOLIDATION
Virtualisation Consolidation
Same
Goal reduce physical servers Goal to reduce physical serversSavings on power licensing maintenance
Savings on power licensing maintenance
Performance concerns Performance concerns
Different
Same number of OS Fewer OSSame databases instance More databases instanceSame number of instances Fewer instancesNo Windows SQL Upgrade Can upgrade Windows and SQLldquoBlack-boxrdquo approach Lots of engineering test effortAdditional layer of technology More mixed workloadHardware abstraction Tight hardware integration
Consolidation Virtualisation
HOW NOW
Affordable performanceMulti-core CPUs64-bit MemoryDisk IO ndash Solid State Disks
Core 1Core 2
Core 3Core 4
CONSOLIDATION DIMENSIONS
Management amp Administrative Processes
StandardsIndependent
Fewer
Physical Locations
Several
O
ne
Mul
tiple
SQ
L In
stan
ces
per
Win
dow
s
Win
dow
s Per
Ser
ver
O
ne
Man
y - V
irtua
lisati
on
DBs p
er
SQL I
nsta
nce
Som
e
Hundr
eds
Some DataDatabaseDuplication
Lot
Current amp ldquoTo Berdquo position along each dimension
CONSOLIDATION CONSIDERDATIONS
Resource requirements of databases Processor memory disk IO and network TempDB usage
Dependencies outside user database Third party support Instance-wide settings security model Replication Log Shipping Database Mirroring
Collation and sort order
BUSINESS DRIVERS
Why consolidate
Reduced costs Standardisation Better server utilisation Space electricity cooling License costsBetter control of IT Processes Consistent operations BaR DR Maintenance
Improved Business Integration
Consolidation activities can reduce costs by 10 percent to 25 percent or more in some casesGartner March 2008
TECHNICAL BENEFITS
Multi-InstanceFlexibility to based on Service Level Agreements (SLA) requirements Performance Backup Recovery Security Change control Operational Upgrade
Multiple development environments on single serverSupport larger workloads on a single serverSeveral trade-offs considerations (more later)
TECHNICAL BENEFITS
Single InstanceAvoid of fixed overhead of multiple instance Fixed server memory configuration Single set of EXEs DLLs etc
Some components are always shared anywayDynamic memory for single instance serverLess administrative workSeveral trade-offs and considerations (more later)
TECHNICAL BENEFITS
Multi-Windows Instance (Virtualisation)
MoreProvides OS IsolationToo many instances decrease value of high end servers
LessReduces scale-up capabilityCan increase risk (single OS point of failure)
HIGH-LEVEL PLANNING
CONSOLIDATION SUCCESS FACTORS
Consolidation
Strategy
People
Process
Technology
HIGH LEVEL PLANNING
Strategy
Motivation for consolidation and end goalsMeasure quantify benefitsEstablish Guiding Principles
People
Potential change in the ownership (DBA Custodianship) of databull Technically Database Ownership (DBO) can be retained
Ongoing support and change managementbull System Administration role change
HIGH LEVEL PLANNING
ProcessAdministrative Operational Performance MonitoringTuning BackupRestore Capacity PlanningMigration and rollback planning
TechnologyCPU memory management IO subsystemWorkload isolationConsolidation ndash name conflicts objects security logins
Management FocusCritical to success
CONSOLIDATION ROADMAP
SQL 2000 2005 amp older
instances
SQL 2008 (2005) Instances
Much More Challenging
One at a time or
en-masse
One at a timeCurrent Environment
ldquoTo Berdquo Environment
bull Monitor behavior
bull Stabilise
Staging Environment
Test amp Production Consolidated
SQL 2008
GUIDING PRINCIPLES
Evaluate Customise and Adopt
Start by consolidating non-mission critical workloadUpgrade to SQL 2008 before consolidating Consolidate similar workloads into single SQL Server instanceAvoid bug fixes during consolidationMaintain transparent user experience Drive standardisation (configuration and operations)
PLANNING DESIGN amp IMPLEMENTATION
PLAN DESIGN IMPLEMENT
Stage 1 ndash Envision1 Current Environment Assessment
Discovery Audit Business Requirements SLA RPO RTO Workload profile transaction volumes processor disk memory SQL Server feature usage Linked servers Extended SP
2 Identify Target Environment amp Develop Consolidation Principles First cut ldquoTo Berdquo environment Discuss gather feedback revise target environment Review financial justification - RoI Develop Consolidation Guiding Principles
PLAN DESIGN IMPLEMENT
Stage 2 ndash Plan amp Design
3 Design lsquoFuturersquo Consolidated Infrastructure Develop design Blueprint Design Review
4 Service User amp Data Migration Planning Migration approach Deployment planning Sequencing of Applications Users Data Design develop migration scripts
PLAN DESIGN IMPLEMENT
Stage 3 ndash Implement
5 Commission consolidated environment for test Test parallel to production Migrate test database
bull Test Migration processbull Load capacity testing highly recommended
Gain confidence in platform and workload profile Isolate identify fix issues
PLAN DESIGN IMPLEMENT
Stage 4 ndash Deploy amp Stabilise
6 Build amp deploy Production Consolidated SQL Service Consolidatemigrate incrementally
bull Capture baselinebull Add incrementally (ONE at a time)bull Stabilisebull Measure again
Transparent User Experience
7 Measure new Service Compare with lsquooldrsquo Retire old servers
TECHNICAL CONSIDERATIONS
MULTI-INSTANCE SERVERS
Min Max server memoryCPU affinity maskWindows System Resource Manager (WSRM)Failover cluster Possible owners Preferred owners AntiAffinityClassName
SERVER1
BIZSQLSQL1
PLANNING MULTI DATABASES
Resource Governor Min max CPU Min max Memory
Un-managed Worker threads TempDB Plan cache
SERVER1
SQL1
VIRTUALISATION DESIGN
Proper hardware sizing criticalGood storage configuration is critical Use fixed or pass-thru disks (avoid dynamic disks) Avoid thin-provisioning Tune storage configuration
Limitations 4 virtual processor per guest 64 cores in host 64 GB memory in host
x64 benefits are significantAvoid over-committing CPU or memoryStart with single VPU
Recommendations
VIRTUALISATION WITH HIGH AVAILABILITY
Virtual machine failoverHigh Availability regardless of Windows or SQL edition
Live Migration with Hyper-V Uses Failover clustering Requires Win 2008 R2 Single host failover
VIRTUALISATION FOR SITE RESILIENCE
Using virtualisation to provide site resilienceSite-to-site disaster recovery
INTERESTING READS
SQL Server Consolidation Whitepaperhttpwwwmicrosoftcomsqlserver2008enuswhite-papersaspx
SQL Server Virtualisation Whitepaperhttpdownloadmicrosoftcomdownloadd94d948f981-926e-40fa-a026-5bfcf076d9b9SQL2008inHyperV2008docx
Microsoft Assessment and Planning Toolkit httpwwwmicrosoftcomdownloadsdetailsaspxFamilyID=67240b76-3148-4e49-943d-4d9ea7f77730ampdisplaylang=en
Windows System Resource Manager (WSRM)httptechnetmicrosoftcomen-uslibrarycc771218(WS10)aspx
SUMMARY
Plan Design Deliver ConsolidationConstruct Guiding Principles
Identify good candidates for consolidationProviding workload
isolationAn approach to consolidating an estate
HOW NOW
Affordable performanceMulti-core CPUs64-bit MemoryDisk IO ndash Solid State Disks
Core 1Core 2
Core 3Core 4
CONSOLIDATION DIMENSIONS
Management amp Administrative Processes
StandardsIndependent
Fewer
Physical Locations
Several
O
ne
Mul
tiple
SQ
L In
stan
ces
per
Win
dow
s
Win
dow
s Per
Ser
ver
O
ne
Man
y - V
irtua
lisati
on
DBs p
er
SQL I
nsta
nce
Som
e
Hundr
eds
Some DataDatabaseDuplication
Lot
Current amp ldquoTo Berdquo position along each dimension
CONSOLIDATION CONSIDERDATIONS
Resource requirements of databases Processor memory disk IO and network TempDB usage
Dependencies outside user database Third party support Instance-wide settings security model Replication Log Shipping Database Mirroring
Collation and sort order
BUSINESS DRIVERS
Why consolidate
Reduced costs Standardisation Better server utilisation Space electricity cooling License costsBetter control of IT Processes Consistent operations BaR DR Maintenance
Improved Business Integration
Consolidation activities can reduce costs by 10 percent to 25 percent or more in some casesGartner March 2008
TECHNICAL BENEFITS
Multi-InstanceFlexibility to based on Service Level Agreements (SLA) requirements Performance Backup Recovery Security Change control Operational Upgrade
Multiple development environments on single serverSupport larger workloads on a single serverSeveral trade-offs considerations (more later)
TECHNICAL BENEFITS
Single InstanceAvoid of fixed overhead of multiple instance Fixed server memory configuration Single set of EXEs DLLs etc
Some components are always shared anywayDynamic memory for single instance serverLess administrative workSeveral trade-offs and considerations (more later)
TECHNICAL BENEFITS
Multi-Windows Instance (Virtualisation)
MoreProvides OS IsolationToo many instances decrease value of high end servers
LessReduces scale-up capabilityCan increase risk (single OS point of failure)
HIGH-LEVEL PLANNING
CONSOLIDATION SUCCESS FACTORS
Consolidation
Strategy
People
Process
Technology
HIGH LEVEL PLANNING
Strategy
Motivation for consolidation and end goalsMeasure quantify benefitsEstablish Guiding Principles
People
Potential change in the ownership (DBA Custodianship) of databull Technically Database Ownership (DBO) can be retained
Ongoing support and change managementbull System Administration role change
HIGH LEVEL PLANNING
ProcessAdministrative Operational Performance MonitoringTuning BackupRestore Capacity PlanningMigration and rollback planning
TechnologyCPU memory management IO subsystemWorkload isolationConsolidation ndash name conflicts objects security logins
Management FocusCritical to success
CONSOLIDATION ROADMAP
SQL 2000 2005 amp older
instances
SQL 2008 (2005) Instances
Much More Challenging
One at a time or
en-masse
One at a timeCurrent Environment
ldquoTo Berdquo Environment
bull Monitor behavior
bull Stabilise
Staging Environment
Test amp Production Consolidated
SQL 2008
GUIDING PRINCIPLES
Evaluate Customise and Adopt
Start by consolidating non-mission critical workloadUpgrade to SQL 2008 before consolidating Consolidate similar workloads into single SQL Server instanceAvoid bug fixes during consolidationMaintain transparent user experience Drive standardisation (configuration and operations)
PLANNING DESIGN amp IMPLEMENTATION
PLAN DESIGN IMPLEMENT
Stage 1 ndash Envision1 Current Environment Assessment
Discovery Audit Business Requirements SLA RPO RTO Workload profile transaction volumes processor disk memory SQL Server feature usage Linked servers Extended SP
2 Identify Target Environment amp Develop Consolidation Principles First cut ldquoTo Berdquo environment Discuss gather feedback revise target environment Review financial justification - RoI Develop Consolidation Guiding Principles
PLAN DESIGN IMPLEMENT
Stage 2 ndash Plan amp Design
3 Design lsquoFuturersquo Consolidated Infrastructure Develop design Blueprint Design Review
4 Service User amp Data Migration Planning Migration approach Deployment planning Sequencing of Applications Users Data Design develop migration scripts
PLAN DESIGN IMPLEMENT
Stage 3 ndash Implement
5 Commission consolidated environment for test Test parallel to production Migrate test database
bull Test Migration processbull Load capacity testing highly recommended
Gain confidence in platform and workload profile Isolate identify fix issues
PLAN DESIGN IMPLEMENT
Stage 4 ndash Deploy amp Stabilise
6 Build amp deploy Production Consolidated SQL Service Consolidatemigrate incrementally
bull Capture baselinebull Add incrementally (ONE at a time)bull Stabilisebull Measure again
Transparent User Experience
7 Measure new Service Compare with lsquooldrsquo Retire old servers
TECHNICAL CONSIDERATIONS
MULTI-INSTANCE SERVERS
Min Max server memoryCPU affinity maskWindows System Resource Manager (WSRM)Failover cluster Possible owners Preferred owners AntiAffinityClassName
SERVER1
BIZSQLSQL1
PLANNING MULTI DATABASES
Resource Governor Min max CPU Min max Memory
Un-managed Worker threads TempDB Plan cache
SERVER1
SQL1
VIRTUALISATION DESIGN
Proper hardware sizing criticalGood storage configuration is critical Use fixed or pass-thru disks (avoid dynamic disks) Avoid thin-provisioning Tune storage configuration
Limitations 4 virtual processor per guest 64 cores in host 64 GB memory in host
x64 benefits are significantAvoid over-committing CPU or memoryStart with single VPU
Recommendations
VIRTUALISATION WITH HIGH AVAILABILITY
Virtual machine failoverHigh Availability regardless of Windows or SQL edition
Live Migration with Hyper-V Uses Failover clustering Requires Win 2008 R2 Single host failover
VIRTUALISATION FOR SITE RESILIENCE
Using virtualisation to provide site resilienceSite-to-site disaster recovery
INTERESTING READS
SQL Server Consolidation Whitepaperhttpwwwmicrosoftcomsqlserver2008enuswhite-papersaspx
SQL Server Virtualisation Whitepaperhttpdownloadmicrosoftcomdownloadd94d948f981-926e-40fa-a026-5bfcf076d9b9SQL2008inHyperV2008docx
Microsoft Assessment and Planning Toolkit httpwwwmicrosoftcomdownloadsdetailsaspxFamilyID=67240b76-3148-4e49-943d-4d9ea7f77730ampdisplaylang=en
Windows System Resource Manager (WSRM)httptechnetmicrosoftcomen-uslibrarycc771218(WS10)aspx
SUMMARY
Plan Design Deliver ConsolidationConstruct Guiding Principles
Identify good candidates for consolidationProviding workload
isolationAn approach to consolidating an estate
CONSOLIDATION DIMENSIONS
Management amp Administrative Processes
StandardsIndependent
Fewer
Physical Locations
Several
O
ne
Mul
tiple
SQ
L In
stan
ces
per
Win
dow
s
Win
dow
s Per
Ser
ver
O
ne
Man
y - V
irtua
lisati
on
DBs p
er
SQL I
nsta
nce
Som
e
Hundr
eds
Some DataDatabaseDuplication
Lot
Current amp ldquoTo Berdquo position along each dimension
CONSOLIDATION CONSIDERDATIONS
Resource requirements of databases Processor memory disk IO and network TempDB usage
Dependencies outside user database Third party support Instance-wide settings security model Replication Log Shipping Database Mirroring
Collation and sort order
BUSINESS DRIVERS
Why consolidate
Reduced costs Standardisation Better server utilisation Space electricity cooling License costsBetter control of IT Processes Consistent operations BaR DR Maintenance
Improved Business Integration
Consolidation activities can reduce costs by 10 percent to 25 percent or more in some casesGartner March 2008
TECHNICAL BENEFITS
Multi-InstanceFlexibility to based on Service Level Agreements (SLA) requirements Performance Backup Recovery Security Change control Operational Upgrade
Multiple development environments on single serverSupport larger workloads on a single serverSeveral trade-offs considerations (more later)
TECHNICAL BENEFITS
Single InstanceAvoid of fixed overhead of multiple instance Fixed server memory configuration Single set of EXEs DLLs etc
Some components are always shared anywayDynamic memory for single instance serverLess administrative workSeveral trade-offs and considerations (more later)
TECHNICAL BENEFITS
Multi-Windows Instance (Virtualisation)
MoreProvides OS IsolationToo many instances decrease value of high end servers
LessReduces scale-up capabilityCan increase risk (single OS point of failure)
HIGH-LEVEL PLANNING
CONSOLIDATION SUCCESS FACTORS
Consolidation
Strategy
People
Process
Technology
HIGH LEVEL PLANNING
Strategy
Motivation for consolidation and end goalsMeasure quantify benefitsEstablish Guiding Principles
People
Potential change in the ownership (DBA Custodianship) of databull Technically Database Ownership (DBO) can be retained
Ongoing support and change managementbull System Administration role change
HIGH LEVEL PLANNING
ProcessAdministrative Operational Performance MonitoringTuning BackupRestore Capacity PlanningMigration and rollback planning
TechnologyCPU memory management IO subsystemWorkload isolationConsolidation ndash name conflicts objects security logins
Management FocusCritical to success
CONSOLIDATION ROADMAP
SQL 2000 2005 amp older
instances
SQL 2008 (2005) Instances
Much More Challenging
One at a time or
en-masse
One at a timeCurrent Environment
ldquoTo Berdquo Environment
bull Monitor behavior
bull Stabilise
Staging Environment
Test amp Production Consolidated
SQL 2008
GUIDING PRINCIPLES
Evaluate Customise and Adopt
Start by consolidating non-mission critical workloadUpgrade to SQL 2008 before consolidating Consolidate similar workloads into single SQL Server instanceAvoid bug fixes during consolidationMaintain transparent user experience Drive standardisation (configuration and operations)
PLANNING DESIGN amp IMPLEMENTATION
PLAN DESIGN IMPLEMENT
Stage 1 ndash Envision1 Current Environment Assessment
Discovery Audit Business Requirements SLA RPO RTO Workload profile transaction volumes processor disk memory SQL Server feature usage Linked servers Extended SP
2 Identify Target Environment amp Develop Consolidation Principles First cut ldquoTo Berdquo environment Discuss gather feedback revise target environment Review financial justification - RoI Develop Consolidation Guiding Principles
PLAN DESIGN IMPLEMENT
Stage 2 ndash Plan amp Design
3 Design lsquoFuturersquo Consolidated Infrastructure Develop design Blueprint Design Review
4 Service User amp Data Migration Planning Migration approach Deployment planning Sequencing of Applications Users Data Design develop migration scripts
PLAN DESIGN IMPLEMENT
Stage 3 ndash Implement
5 Commission consolidated environment for test Test parallel to production Migrate test database
bull Test Migration processbull Load capacity testing highly recommended
Gain confidence in platform and workload profile Isolate identify fix issues
PLAN DESIGN IMPLEMENT
Stage 4 ndash Deploy amp Stabilise
6 Build amp deploy Production Consolidated SQL Service Consolidatemigrate incrementally
bull Capture baselinebull Add incrementally (ONE at a time)bull Stabilisebull Measure again
Transparent User Experience
7 Measure new Service Compare with lsquooldrsquo Retire old servers
TECHNICAL CONSIDERATIONS
MULTI-INSTANCE SERVERS
Min Max server memoryCPU affinity maskWindows System Resource Manager (WSRM)Failover cluster Possible owners Preferred owners AntiAffinityClassName
SERVER1
BIZSQLSQL1
PLANNING MULTI DATABASES
Resource Governor Min max CPU Min max Memory
Un-managed Worker threads TempDB Plan cache
SERVER1
SQL1
VIRTUALISATION DESIGN
Proper hardware sizing criticalGood storage configuration is critical Use fixed or pass-thru disks (avoid dynamic disks) Avoid thin-provisioning Tune storage configuration
Limitations 4 virtual processor per guest 64 cores in host 64 GB memory in host
x64 benefits are significantAvoid over-committing CPU or memoryStart with single VPU
Recommendations
VIRTUALISATION WITH HIGH AVAILABILITY
Virtual machine failoverHigh Availability regardless of Windows or SQL edition
Live Migration with Hyper-V Uses Failover clustering Requires Win 2008 R2 Single host failover
VIRTUALISATION FOR SITE RESILIENCE
Using virtualisation to provide site resilienceSite-to-site disaster recovery
INTERESTING READS
SQL Server Consolidation Whitepaperhttpwwwmicrosoftcomsqlserver2008enuswhite-papersaspx
SQL Server Virtualisation Whitepaperhttpdownloadmicrosoftcomdownloadd94d948f981-926e-40fa-a026-5bfcf076d9b9SQL2008inHyperV2008docx
Microsoft Assessment and Planning Toolkit httpwwwmicrosoftcomdownloadsdetailsaspxFamilyID=67240b76-3148-4e49-943d-4d9ea7f77730ampdisplaylang=en
Windows System Resource Manager (WSRM)httptechnetmicrosoftcomen-uslibrarycc771218(WS10)aspx
SUMMARY
Plan Design Deliver ConsolidationConstruct Guiding Principles
Identify good candidates for consolidationProviding workload
isolationAn approach to consolidating an estate
CONSOLIDATION CONSIDERDATIONS
Resource requirements of databases Processor memory disk IO and network TempDB usage
Dependencies outside user database Third party support Instance-wide settings security model Replication Log Shipping Database Mirroring
Collation and sort order
BUSINESS DRIVERS
Why consolidate
Reduced costs Standardisation Better server utilisation Space electricity cooling License costsBetter control of IT Processes Consistent operations BaR DR Maintenance
Improved Business Integration
Consolidation activities can reduce costs by 10 percent to 25 percent or more in some casesGartner March 2008
TECHNICAL BENEFITS
Multi-InstanceFlexibility to based on Service Level Agreements (SLA) requirements Performance Backup Recovery Security Change control Operational Upgrade
Multiple development environments on single serverSupport larger workloads on a single serverSeveral trade-offs considerations (more later)
TECHNICAL BENEFITS
Single InstanceAvoid of fixed overhead of multiple instance Fixed server memory configuration Single set of EXEs DLLs etc
Some components are always shared anywayDynamic memory for single instance serverLess administrative workSeveral trade-offs and considerations (more later)
TECHNICAL BENEFITS
Multi-Windows Instance (Virtualisation)
MoreProvides OS IsolationToo many instances decrease value of high end servers
LessReduces scale-up capabilityCan increase risk (single OS point of failure)
HIGH-LEVEL PLANNING
CONSOLIDATION SUCCESS FACTORS
Consolidation
Strategy
People
Process
Technology
HIGH LEVEL PLANNING
Strategy
Motivation for consolidation and end goalsMeasure quantify benefitsEstablish Guiding Principles
People
Potential change in the ownership (DBA Custodianship) of databull Technically Database Ownership (DBO) can be retained
Ongoing support and change managementbull System Administration role change
HIGH LEVEL PLANNING
ProcessAdministrative Operational Performance MonitoringTuning BackupRestore Capacity PlanningMigration and rollback planning
TechnologyCPU memory management IO subsystemWorkload isolationConsolidation ndash name conflicts objects security logins
Management FocusCritical to success
CONSOLIDATION ROADMAP
SQL 2000 2005 amp older
instances
SQL 2008 (2005) Instances
Much More Challenging
One at a time or
en-masse
One at a timeCurrent Environment
ldquoTo Berdquo Environment
bull Monitor behavior
bull Stabilise
Staging Environment
Test amp Production Consolidated
SQL 2008
GUIDING PRINCIPLES
Evaluate Customise and Adopt
Start by consolidating non-mission critical workloadUpgrade to SQL 2008 before consolidating Consolidate similar workloads into single SQL Server instanceAvoid bug fixes during consolidationMaintain transparent user experience Drive standardisation (configuration and operations)
PLANNING DESIGN amp IMPLEMENTATION
PLAN DESIGN IMPLEMENT
Stage 1 ndash Envision1 Current Environment Assessment
Discovery Audit Business Requirements SLA RPO RTO Workload profile transaction volumes processor disk memory SQL Server feature usage Linked servers Extended SP
2 Identify Target Environment amp Develop Consolidation Principles First cut ldquoTo Berdquo environment Discuss gather feedback revise target environment Review financial justification - RoI Develop Consolidation Guiding Principles
PLAN DESIGN IMPLEMENT
Stage 2 ndash Plan amp Design
3 Design lsquoFuturersquo Consolidated Infrastructure Develop design Blueprint Design Review
4 Service User amp Data Migration Planning Migration approach Deployment planning Sequencing of Applications Users Data Design develop migration scripts
PLAN DESIGN IMPLEMENT
Stage 3 ndash Implement
5 Commission consolidated environment for test Test parallel to production Migrate test database
bull Test Migration processbull Load capacity testing highly recommended
Gain confidence in platform and workload profile Isolate identify fix issues
PLAN DESIGN IMPLEMENT
Stage 4 ndash Deploy amp Stabilise
6 Build amp deploy Production Consolidated SQL Service Consolidatemigrate incrementally
bull Capture baselinebull Add incrementally (ONE at a time)bull Stabilisebull Measure again
Transparent User Experience
7 Measure new Service Compare with lsquooldrsquo Retire old servers
TECHNICAL CONSIDERATIONS
MULTI-INSTANCE SERVERS
Min Max server memoryCPU affinity maskWindows System Resource Manager (WSRM)Failover cluster Possible owners Preferred owners AntiAffinityClassName
SERVER1
BIZSQLSQL1
PLANNING MULTI DATABASES
Resource Governor Min max CPU Min max Memory
Un-managed Worker threads TempDB Plan cache
SERVER1
SQL1
VIRTUALISATION DESIGN
Proper hardware sizing criticalGood storage configuration is critical Use fixed or pass-thru disks (avoid dynamic disks) Avoid thin-provisioning Tune storage configuration
Limitations 4 virtual processor per guest 64 cores in host 64 GB memory in host
x64 benefits are significantAvoid over-committing CPU or memoryStart with single VPU
Recommendations
VIRTUALISATION WITH HIGH AVAILABILITY
Virtual machine failoverHigh Availability regardless of Windows or SQL edition
Live Migration with Hyper-V Uses Failover clustering Requires Win 2008 R2 Single host failover
VIRTUALISATION FOR SITE RESILIENCE
Using virtualisation to provide site resilienceSite-to-site disaster recovery
INTERESTING READS
SQL Server Consolidation Whitepaperhttpwwwmicrosoftcomsqlserver2008enuswhite-papersaspx
SQL Server Virtualisation Whitepaperhttpdownloadmicrosoftcomdownloadd94d948f981-926e-40fa-a026-5bfcf076d9b9SQL2008inHyperV2008docx
Microsoft Assessment and Planning Toolkit httpwwwmicrosoftcomdownloadsdetailsaspxFamilyID=67240b76-3148-4e49-943d-4d9ea7f77730ampdisplaylang=en
Windows System Resource Manager (WSRM)httptechnetmicrosoftcomen-uslibrarycc771218(WS10)aspx
SUMMARY
Plan Design Deliver ConsolidationConstruct Guiding Principles
Identify good candidates for consolidationProviding workload
isolationAn approach to consolidating an estate
BUSINESS DRIVERS
Why consolidate
Reduced costs Standardisation Better server utilisation Space electricity cooling License costsBetter control of IT Processes Consistent operations BaR DR Maintenance
Improved Business Integration
Consolidation activities can reduce costs by 10 percent to 25 percent or more in some casesGartner March 2008
TECHNICAL BENEFITS
Multi-InstanceFlexibility to based on Service Level Agreements (SLA) requirements Performance Backup Recovery Security Change control Operational Upgrade
Multiple development environments on single serverSupport larger workloads on a single serverSeveral trade-offs considerations (more later)
TECHNICAL BENEFITS
Single InstanceAvoid of fixed overhead of multiple instance Fixed server memory configuration Single set of EXEs DLLs etc
Some components are always shared anywayDynamic memory for single instance serverLess administrative workSeveral trade-offs and considerations (more later)
TECHNICAL BENEFITS
Multi-Windows Instance (Virtualisation)
MoreProvides OS IsolationToo many instances decrease value of high end servers
LessReduces scale-up capabilityCan increase risk (single OS point of failure)
HIGH-LEVEL PLANNING
CONSOLIDATION SUCCESS FACTORS
Consolidation
Strategy
People
Process
Technology
HIGH LEVEL PLANNING
Strategy
Motivation for consolidation and end goalsMeasure quantify benefitsEstablish Guiding Principles
People
Potential change in the ownership (DBA Custodianship) of databull Technically Database Ownership (DBO) can be retained
Ongoing support and change managementbull System Administration role change
HIGH LEVEL PLANNING
ProcessAdministrative Operational Performance MonitoringTuning BackupRestore Capacity PlanningMigration and rollback planning
TechnologyCPU memory management IO subsystemWorkload isolationConsolidation ndash name conflicts objects security logins
Management FocusCritical to success
CONSOLIDATION ROADMAP
SQL 2000 2005 amp older
instances
SQL 2008 (2005) Instances
Much More Challenging
One at a time or
en-masse
One at a timeCurrent Environment
ldquoTo Berdquo Environment
bull Monitor behavior
bull Stabilise
Staging Environment
Test amp Production Consolidated
SQL 2008
GUIDING PRINCIPLES
Evaluate Customise and Adopt
Start by consolidating non-mission critical workloadUpgrade to SQL 2008 before consolidating Consolidate similar workloads into single SQL Server instanceAvoid bug fixes during consolidationMaintain transparent user experience Drive standardisation (configuration and operations)
PLANNING DESIGN amp IMPLEMENTATION
PLAN DESIGN IMPLEMENT
Stage 1 ndash Envision1 Current Environment Assessment
Discovery Audit Business Requirements SLA RPO RTO Workload profile transaction volumes processor disk memory SQL Server feature usage Linked servers Extended SP
2 Identify Target Environment amp Develop Consolidation Principles First cut ldquoTo Berdquo environment Discuss gather feedback revise target environment Review financial justification - RoI Develop Consolidation Guiding Principles
PLAN DESIGN IMPLEMENT
Stage 2 ndash Plan amp Design
3 Design lsquoFuturersquo Consolidated Infrastructure Develop design Blueprint Design Review
4 Service User amp Data Migration Planning Migration approach Deployment planning Sequencing of Applications Users Data Design develop migration scripts
PLAN DESIGN IMPLEMENT
Stage 3 ndash Implement
5 Commission consolidated environment for test Test parallel to production Migrate test database
bull Test Migration processbull Load capacity testing highly recommended
Gain confidence in platform and workload profile Isolate identify fix issues
PLAN DESIGN IMPLEMENT
Stage 4 ndash Deploy amp Stabilise
6 Build amp deploy Production Consolidated SQL Service Consolidatemigrate incrementally
bull Capture baselinebull Add incrementally (ONE at a time)bull Stabilisebull Measure again
Transparent User Experience
7 Measure new Service Compare with lsquooldrsquo Retire old servers
TECHNICAL CONSIDERATIONS
MULTI-INSTANCE SERVERS
Min Max server memoryCPU affinity maskWindows System Resource Manager (WSRM)Failover cluster Possible owners Preferred owners AntiAffinityClassName
SERVER1
BIZSQLSQL1
PLANNING MULTI DATABASES
Resource Governor Min max CPU Min max Memory
Un-managed Worker threads TempDB Plan cache
SERVER1
SQL1
VIRTUALISATION DESIGN
Proper hardware sizing criticalGood storage configuration is critical Use fixed or pass-thru disks (avoid dynamic disks) Avoid thin-provisioning Tune storage configuration
Limitations 4 virtual processor per guest 64 cores in host 64 GB memory in host
x64 benefits are significantAvoid over-committing CPU or memoryStart with single VPU
Recommendations
VIRTUALISATION WITH HIGH AVAILABILITY
Virtual machine failoverHigh Availability regardless of Windows or SQL edition
Live Migration with Hyper-V Uses Failover clustering Requires Win 2008 R2 Single host failover
VIRTUALISATION FOR SITE RESILIENCE
Using virtualisation to provide site resilienceSite-to-site disaster recovery
INTERESTING READS
SQL Server Consolidation Whitepaperhttpwwwmicrosoftcomsqlserver2008enuswhite-papersaspx
SQL Server Virtualisation Whitepaperhttpdownloadmicrosoftcomdownloadd94d948f981-926e-40fa-a026-5bfcf076d9b9SQL2008inHyperV2008docx
Microsoft Assessment and Planning Toolkit httpwwwmicrosoftcomdownloadsdetailsaspxFamilyID=67240b76-3148-4e49-943d-4d9ea7f77730ampdisplaylang=en
Windows System Resource Manager (WSRM)httptechnetmicrosoftcomen-uslibrarycc771218(WS10)aspx
SUMMARY
Plan Design Deliver ConsolidationConstruct Guiding Principles
Identify good candidates for consolidationProviding workload
isolationAn approach to consolidating an estate
TECHNICAL BENEFITS
Multi-InstanceFlexibility to based on Service Level Agreements (SLA) requirements Performance Backup Recovery Security Change control Operational Upgrade
Multiple development environments on single serverSupport larger workloads on a single serverSeveral trade-offs considerations (more later)
TECHNICAL BENEFITS
Single InstanceAvoid of fixed overhead of multiple instance Fixed server memory configuration Single set of EXEs DLLs etc
Some components are always shared anywayDynamic memory for single instance serverLess administrative workSeveral trade-offs and considerations (more later)
TECHNICAL BENEFITS
Multi-Windows Instance (Virtualisation)
MoreProvides OS IsolationToo many instances decrease value of high end servers
LessReduces scale-up capabilityCan increase risk (single OS point of failure)
HIGH-LEVEL PLANNING
CONSOLIDATION SUCCESS FACTORS
Consolidation
Strategy
People
Process
Technology
HIGH LEVEL PLANNING
Strategy
Motivation for consolidation and end goalsMeasure quantify benefitsEstablish Guiding Principles
People
Potential change in the ownership (DBA Custodianship) of databull Technically Database Ownership (DBO) can be retained
Ongoing support and change managementbull System Administration role change
HIGH LEVEL PLANNING
ProcessAdministrative Operational Performance MonitoringTuning BackupRestore Capacity PlanningMigration and rollback planning
TechnologyCPU memory management IO subsystemWorkload isolationConsolidation ndash name conflicts objects security logins
Management FocusCritical to success
CONSOLIDATION ROADMAP
SQL 2000 2005 amp older
instances
SQL 2008 (2005) Instances
Much More Challenging
One at a time or
en-masse
One at a timeCurrent Environment
ldquoTo Berdquo Environment
bull Monitor behavior
bull Stabilise
Staging Environment
Test amp Production Consolidated
SQL 2008
GUIDING PRINCIPLES
Evaluate Customise and Adopt
Start by consolidating non-mission critical workloadUpgrade to SQL 2008 before consolidating Consolidate similar workloads into single SQL Server instanceAvoid bug fixes during consolidationMaintain transparent user experience Drive standardisation (configuration and operations)
PLANNING DESIGN amp IMPLEMENTATION
PLAN DESIGN IMPLEMENT
Stage 1 ndash Envision1 Current Environment Assessment
Discovery Audit Business Requirements SLA RPO RTO Workload profile transaction volumes processor disk memory SQL Server feature usage Linked servers Extended SP
2 Identify Target Environment amp Develop Consolidation Principles First cut ldquoTo Berdquo environment Discuss gather feedback revise target environment Review financial justification - RoI Develop Consolidation Guiding Principles
PLAN DESIGN IMPLEMENT
Stage 2 ndash Plan amp Design
3 Design lsquoFuturersquo Consolidated Infrastructure Develop design Blueprint Design Review
4 Service User amp Data Migration Planning Migration approach Deployment planning Sequencing of Applications Users Data Design develop migration scripts
PLAN DESIGN IMPLEMENT
Stage 3 ndash Implement
5 Commission consolidated environment for test Test parallel to production Migrate test database
bull Test Migration processbull Load capacity testing highly recommended
Gain confidence in platform and workload profile Isolate identify fix issues
PLAN DESIGN IMPLEMENT
Stage 4 ndash Deploy amp Stabilise
6 Build amp deploy Production Consolidated SQL Service Consolidatemigrate incrementally
bull Capture baselinebull Add incrementally (ONE at a time)bull Stabilisebull Measure again
Transparent User Experience
7 Measure new Service Compare with lsquooldrsquo Retire old servers
TECHNICAL CONSIDERATIONS
MULTI-INSTANCE SERVERS
Min Max server memoryCPU affinity maskWindows System Resource Manager (WSRM)Failover cluster Possible owners Preferred owners AntiAffinityClassName
SERVER1
BIZSQLSQL1
PLANNING MULTI DATABASES
Resource Governor Min max CPU Min max Memory
Un-managed Worker threads TempDB Plan cache
SERVER1
SQL1
VIRTUALISATION DESIGN
Proper hardware sizing criticalGood storage configuration is critical Use fixed or pass-thru disks (avoid dynamic disks) Avoid thin-provisioning Tune storage configuration
Limitations 4 virtual processor per guest 64 cores in host 64 GB memory in host
x64 benefits are significantAvoid over-committing CPU or memoryStart with single VPU
Recommendations
VIRTUALISATION WITH HIGH AVAILABILITY
Virtual machine failoverHigh Availability regardless of Windows or SQL edition
Live Migration with Hyper-V Uses Failover clustering Requires Win 2008 R2 Single host failover
VIRTUALISATION FOR SITE RESILIENCE
Using virtualisation to provide site resilienceSite-to-site disaster recovery
INTERESTING READS
SQL Server Consolidation Whitepaperhttpwwwmicrosoftcomsqlserver2008enuswhite-papersaspx
SQL Server Virtualisation Whitepaperhttpdownloadmicrosoftcomdownloadd94d948f981-926e-40fa-a026-5bfcf076d9b9SQL2008inHyperV2008docx
Microsoft Assessment and Planning Toolkit httpwwwmicrosoftcomdownloadsdetailsaspxFamilyID=67240b76-3148-4e49-943d-4d9ea7f77730ampdisplaylang=en
Windows System Resource Manager (WSRM)httptechnetmicrosoftcomen-uslibrarycc771218(WS10)aspx
SUMMARY
Plan Design Deliver ConsolidationConstruct Guiding Principles
Identify good candidates for consolidationProviding workload
isolationAn approach to consolidating an estate
TECHNICAL BENEFITS
Single InstanceAvoid of fixed overhead of multiple instance Fixed server memory configuration Single set of EXEs DLLs etc
Some components are always shared anywayDynamic memory for single instance serverLess administrative workSeveral trade-offs and considerations (more later)
TECHNICAL BENEFITS
Multi-Windows Instance (Virtualisation)
MoreProvides OS IsolationToo many instances decrease value of high end servers
LessReduces scale-up capabilityCan increase risk (single OS point of failure)
HIGH-LEVEL PLANNING
CONSOLIDATION SUCCESS FACTORS
Consolidation
Strategy
People
Process
Technology
HIGH LEVEL PLANNING
Strategy
Motivation for consolidation and end goalsMeasure quantify benefitsEstablish Guiding Principles
People
Potential change in the ownership (DBA Custodianship) of databull Technically Database Ownership (DBO) can be retained
Ongoing support and change managementbull System Administration role change
HIGH LEVEL PLANNING
ProcessAdministrative Operational Performance MonitoringTuning BackupRestore Capacity PlanningMigration and rollback planning
TechnologyCPU memory management IO subsystemWorkload isolationConsolidation ndash name conflicts objects security logins
Management FocusCritical to success
CONSOLIDATION ROADMAP
SQL 2000 2005 amp older
instances
SQL 2008 (2005) Instances
Much More Challenging
One at a time or
en-masse
One at a timeCurrent Environment
ldquoTo Berdquo Environment
bull Monitor behavior
bull Stabilise
Staging Environment
Test amp Production Consolidated
SQL 2008
GUIDING PRINCIPLES
Evaluate Customise and Adopt
Start by consolidating non-mission critical workloadUpgrade to SQL 2008 before consolidating Consolidate similar workloads into single SQL Server instanceAvoid bug fixes during consolidationMaintain transparent user experience Drive standardisation (configuration and operations)
PLANNING DESIGN amp IMPLEMENTATION
PLAN DESIGN IMPLEMENT
Stage 1 ndash Envision1 Current Environment Assessment
Discovery Audit Business Requirements SLA RPO RTO Workload profile transaction volumes processor disk memory SQL Server feature usage Linked servers Extended SP
2 Identify Target Environment amp Develop Consolidation Principles First cut ldquoTo Berdquo environment Discuss gather feedback revise target environment Review financial justification - RoI Develop Consolidation Guiding Principles
PLAN DESIGN IMPLEMENT
Stage 2 ndash Plan amp Design
3 Design lsquoFuturersquo Consolidated Infrastructure Develop design Blueprint Design Review
4 Service User amp Data Migration Planning Migration approach Deployment planning Sequencing of Applications Users Data Design develop migration scripts
PLAN DESIGN IMPLEMENT
Stage 3 ndash Implement
5 Commission consolidated environment for test Test parallel to production Migrate test database
bull Test Migration processbull Load capacity testing highly recommended
Gain confidence in platform and workload profile Isolate identify fix issues
PLAN DESIGN IMPLEMENT
Stage 4 ndash Deploy amp Stabilise
6 Build amp deploy Production Consolidated SQL Service Consolidatemigrate incrementally
bull Capture baselinebull Add incrementally (ONE at a time)bull Stabilisebull Measure again
Transparent User Experience
7 Measure new Service Compare with lsquooldrsquo Retire old servers
TECHNICAL CONSIDERATIONS
MULTI-INSTANCE SERVERS
Min Max server memoryCPU affinity maskWindows System Resource Manager (WSRM)Failover cluster Possible owners Preferred owners AntiAffinityClassName
SERVER1
BIZSQLSQL1
PLANNING MULTI DATABASES
Resource Governor Min max CPU Min max Memory
Un-managed Worker threads TempDB Plan cache
SERVER1
SQL1
VIRTUALISATION DESIGN
Proper hardware sizing criticalGood storage configuration is critical Use fixed or pass-thru disks (avoid dynamic disks) Avoid thin-provisioning Tune storage configuration
Limitations 4 virtual processor per guest 64 cores in host 64 GB memory in host
x64 benefits are significantAvoid over-committing CPU or memoryStart with single VPU
Recommendations
VIRTUALISATION WITH HIGH AVAILABILITY
Virtual machine failoverHigh Availability regardless of Windows or SQL edition
Live Migration with Hyper-V Uses Failover clustering Requires Win 2008 R2 Single host failover
VIRTUALISATION FOR SITE RESILIENCE
Using virtualisation to provide site resilienceSite-to-site disaster recovery
INTERESTING READS
SQL Server Consolidation Whitepaperhttpwwwmicrosoftcomsqlserver2008enuswhite-papersaspx
SQL Server Virtualisation Whitepaperhttpdownloadmicrosoftcomdownloadd94d948f981-926e-40fa-a026-5bfcf076d9b9SQL2008inHyperV2008docx
Microsoft Assessment and Planning Toolkit httpwwwmicrosoftcomdownloadsdetailsaspxFamilyID=67240b76-3148-4e49-943d-4d9ea7f77730ampdisplaylang=en
Windows System Resource Manager (WSRM)httptechnetmicrosoftcomen-uslibrarycc771218(WS10)aspx
SUMMARY
Plan Design Deliver ConsolidationConstruct Guiding Principles
Identify good candidates for consolidationProviding workload
isolationAn approach to consolidating an estate
TECHNICAL BENEFITS
Multi-Windows Instance (Virtualisation)
MoreProvides OS IsolationToo many instances decrease value of high end servers
LessReduces scale-up capabilityCan increase risk (single OS point of failure)
HIGH-LEVEL PLANNING
CONSOLIDATION SUCCESS FACTORS
Consolidation
Strategy
People
Process
Technology
HIGH LEVEL PLANNING
Strategy
Motivation for consolidation and end goalsMeasure quantify benefitsEstablish Guiding Principles
People
Potential change in the ownership (DBA Custodianship) of databull Technically Database Ownership (DBO) can be retained
Ongoing support and change managementbull System Administration role change
HIGH LEVEL PLANNING
ProcessAdministrative Operational Performance MonitoringTuning BackupRestore Capacity PlanningMigration and rollback planning
TechnologyCPU memory management IO subsystemWorkload isolationConsolidation ndash name conflicts objects security logins
Management FocusCritical to success
CONSOLIDATION ROADMAP
SQL 2000 2005 amp older
instances
SQL 2008 (2005) Instances
Much More Challenging
One at a time or
en-masse
One at a timeCurrent Environment
ldquoTo Berdquo Environment
bull Monitor behavior
bull Stabilise
Staging Environment
Test amp Production Consolidated
SQL 2008
GUIDING PRINCIPLES
Evaluate Customise and Adopt
Start by consolidating non-mission critical workloadUpgrade to SQL 2008 before consolidating Consolidate similar workloads into single SQL Server instanceAvoid bug fixes during consolidationMaintain transparent user experience Drive standardisation (configuration and operations)
PLANNING DESIGN amp IMPLEMENTATION
PLAN DESIGN IMPLEMENT
Stage 1 ndash Envision1 Current Environment Assessment
Discovery Audit Business Requirements SLA RPO RTO Workload profile transaction volumes processor disk memory SQL Server feature usage Linked servers Extended SP
2 Identify Target Environment amp Develop Consolidation Principles First cut ldquoTo Berdquo environment Discuss gather feedback revise target environment Review financial justification - RoI Develop Consolidation Guiding Principles
PLAN DESIGN IMPLEMENT
Stage 2 ndash Plan amp Design
3 Design lsquoFuturersquo Consolidated Infrastructure Develop design Blueprint Design Review
4 Service User amp Data Migration Planning Migration approach Deployment planning Sequencing of Applications Users Data Design develop migration scripts
PLAN DESIGN IMPLEMENT
Stage 3 ndash Implement
5 Commission consolidated environment for test Test parallel to production Migrate test database
bull Test Migration processbull Load capacity testing highly recommended
Gain confidence in platform and workload profile Isolate identify fix issues
PLAN DESIGN IMPLEMENT
Stage 4 ndash Deploy amp Stabilise
6 Build amp deploy Production Consolidated SQL Service Consolidatemigrate incrementally
bull Capture baselinebull Add incrementally (ONE at a time)bull Stabilisebull Measure again
Transparent User Experience
7 Measure new Service Compare with lsquooldrsquo Retire old servers
TECHNICAL CONSIDERATIONS
MULTI-INSTANCE SERVERS
Min Max server memoryCPU affinity maskWindows System Resource Manager (WSRM)Failover cluster Possible owners Preferred owners AntiAffinityClassName
SERVER1
BIZSQLSQL1
PLANNING MULTI DATABASES
Resource Governor Min max CPU Min max Memory
Un-managed Worker threads TempDB Plan cache
SERVER1
SQL1
VIRTUALISATION DESIGN
Proper hardware sizing criticalGood storage configuration is critical Use fixed or pass-thru disks (avoid dynamic disks) Avoid thin-provisioning Tune storage configuration
Limitations 4 virtual processor per guest 64 cores in host 64 GB memory in host
x64 benefits are significantAvoid over-committing CPU or memoryStart with single VPU
Recommendations
VIRTUALISATION WITH HIGH AVAILABILITY
Virtual machine failoverHigh Availability regardless of Windows or SQL edition
Live Migration with Hyper-V Uses Failover clustering Requires Win 2008 R2 Single host failover
VIRTUALISATION FOR SITE RESILIENCE
Using virtualisation to provide site resilienceSite-to-site disaster recovery
INTERESTING READS
SQL Server Consolidation Whitepaperhttpwwwmicrosoftcomsqlserver2008enuswhite-papersaspx
SQL Server Virtualisation Whitepaperhttpdownloadmicrosoftcomdownloadd94d948f981-926e-40fa-a026-5bfcf076d9b9SQL2008inHyperV2008docx
Microsoft Assessment and Planning Toolkit httpwwwmicrosoftcomdownloadsdetailsaspxFamilyID=67240b76-3148-4e49-943d-4d9ea7f77730ampdisplaylang=en
Windows System Resource Manager (WSRM)httptechnetmicrosoftcomen-uslibrarycc771218(WS10)aspx
SUMMARY
Plan Design Deliver ConsolidationConstruct Guiding Principles
Identify good candidates for consolidationProviding workload
isolationAn approach to consolidating an estate
HIGH-LEVEL PLANNING
CONSOLIDATION SUCCESS FACTORS
Consolidation
Strategy
People
Process
Technology
HIGH LEVEL PLANNING
Strategy
Motivation for consolidation and end goalsMeasure quantify benefitsEstablish Guiding Principles
People
Potential change in the ownership (DBA Custodianship) of databull Technically Database Ownership (DBO) can be retained
Ongoing support and change managementbull System Administration role change
HIGH LEVEL PLANNING
ProcessAdministrative Operational Performance MonitoringTuning BackupRestore Capacity PlanningMigration and rollback planning
TechnologyCPU memory management IO subsystemWorkload isolationConsolidation ndash name conflicts objects security logins
Management FocusCritical to success
CONSOLIDATION ROADMAP
SQL 2000 2005 amp older
instances
SQL 2008 (2005) Instances
Much More Challenging
One at a time or
en-masse
One at a timeCurrent Environment
ldquoTo Berdquo Environment
bull Monitor behavior
bull Stabilise
Staging Environment
Test amp Production Consolidated
SQL 2008
GUIDING PRINCIPLES
Evaluate Customise and Adopt
Start by consolidating non-mission critical workloadUpgrade to SQL 2008 before consolidating Consolidate similar workloads into single SQL Server instanceAvoid bug fixes during consolidationMaintain transparent user experience Drive standardisation (configuration and operations)
PLANNING DESIGN amp IMPLEMENTATION
PLAN DESIGN IMPLEMENT
Stage 1 ndash Envision1 Current Environment Assessment
Discovery Audit Business Requirements SLA RPO RTO Workload profile transaction volumes processor disk memory SQL Server feature usage Linked servers Extended SP
2 Identify Target Environment amp Develop Consolidation Principles First cut ldquoTo Berdquo environment Discuss gather feedback revise target environment Review financial justification - RoI Develop Consolidation Guiding Principles
PLAN DESIGN IMPLEMENT
Stage 2 ndash Plan amp Design
3 Design lsquoFuturersquo Consolidated Infrastructure Develop design Blueprint Design Review
4 Service User amp Data Migration Planning Migration approach Deployment planning Sequencing of Applications Users Data Design develop migration scripts
PLAN DESIGN IMPLEMENT
Stage 3 ndash Implement
5 Commission consolidated environment for test Test parallel to production Migrate test database
bull Test Migration processbull Load capacity testing highly recommended
Gain confidence in platform and workload profile Isolate identify fix issues
PLAN DESIGN IMPLEMENT
Stage 4 ndash Deploy amp Stabilise
6 Build amp deploy Production Consolidated SQL Service Consolidatemigrate incrementally
bull Capture baselinebull Add incrementally (ONE at a time)bull Stabilisebull Measure again
Transparent User Experience
7 Measure new Service Compare with lsquooldrsquo Retire old servers
TECHNICAL CONSIDERATIONS
MULTI-INSTANCE SERVERS
Min Max server memoryCPU affinity maskWindows System Resource Manager (WSRM)Failover cluster Possible owners Preferred owners AntiAffinityClassName
SERVER1
BIZSQLSQL1
PLANNING MULTI DATABASES
Resource Governor Min max CPU Min max Memory
Un-managed Worker threads TempDB Plan cache
SERVER1
SQL1
VIRTUALISATION DESIGN
Proper hardware sizing criticalGood storage configuration is critical Use fixed or pass-thru disks (avoid dynamic disks) Avoid thin-provisioning Tune storage configuration
Limitations 4 virtual processor per guest 64 cores in host 64 GB memory in host
x64 benefits are significantAvoid over-committing CPU or memoryStart with single VPU
Recommendations
VIRTUALISATION WITH HIGH AVAILABILITY
Virtual machine failoverHigh Availability regardless of Windows or SQL edition
Live Migration with Hyper-V Uses Failover clustering Requires Win 2008 R2 Single host failover
VIRTUALISATION FOR SITE RESILIENCE
Using virtualisation to provide site resilienceSite-to-site disaster recovery
INTERESTING READS
SQL Server Consolidation Whitepaperhttpwwwmicrosoftcomsqlserver2008enuswhite-papersaspx
SQL Server Virtualisation Whitepaperhttpdownloadmicrosoftcomdownloadd94d948f981-926e-40fa-a026-5bfcf076d9b9SQL2008inHyperV2008docx
Microsoft Assessment and Planning Toolkit httpwwwmicrosoftcomdownloadsdetailsaspxFamilyID=67240b76-3148-4e49-943d-4d9ea7f77730ampdisplaylang=en
Windows System Resource Manager (WSRM)httptechnetmicrosoftcomen-uslibrarycc771218(WS10)aspx
SUMMARY
Plan Design Deliver ConsolidationConstruct Guiding Principles
Identify good candidates for consolidationProviding workload
isolationAn approach to consolidating an estate
CONSOLIDATION SUCCESS FACTORS
Consolidation
Strategy
People
Process
Technology
HIGH LEVEL PLANNING
Strategy
Motivation for consolidation and end goalsMeasure quantify benefitsEstablish Guiding Principles
People
Potential change in the ownership (DBA Custodianship) of databull Technically Database Ownership (DBO) can be retained
Ongoing support and change managementbull System Administration role change
HIGH LEVEL PLANNING
ProcessAdministrative Operational Performance MonitoringTuning BackupRestore Capacity PlanningMigration and rollback planning
TechnologyCPU memory management IO subsystemWorkload isolationConsolidation ndash name conflicts objects security logins
Management FocusCritical to success
CONSOLIDATION ROADMAP
SQL 2000 2005 amp older
instances
SQL 2008 (2005) Instances
Much More Challenging
One at a time or
en-masse
One at a timeCurrent Environment
ldquoTo Berdquo Environment
bull Monitor behavior
bull Stabilise
Staging Environment
Test amp Production Consolidated
SQL 2008
GUIDING PRINCIPLES
Evaluate Customise and Adopt
Start by consolidating non-mission critical workloadUpgrade to SQL 2008 before consolidating Consolidate similar workloads into single SQL Server instanceAvoid bug fixes during consolidationMaintain transparent user experience Drive standardisation (configuration and operations)
PLANNING DESIGN amp IMPLEMENTATION
PLAN DESIGN IMPLEMENT
Stage 1 ndash Envision1 Current Environment Assessment
Discovery Audit Business Requirements SLA RPO RTO Workload profile transaction volumes processor disk memory SQL Server feature usage Linked servers Extended SP
2 Identify Target Environment amp Develop Consolidation Principles First cut ldquoTo Berdquo environment Discuss gather feedback revise target environment Review financial justification - RoI Develop Consolidation Guiding Principles
PLAN DESIGN IMPLEMENT
Stage 2 ndash Plan amp Design
3 Design lsquoFuturersquo Consolidated Infrastructure Develop design Blueprint Design Review
4 Service User amp Data Migration Planning Migration approach Deployment planning Sequencing of Applications Users Data Design develop migration scripts
PLAN DESIGN IMPLEMENT
Stage 3 ndash Implement
5 Commission consolidated environment for test Test parallel to production Migrate test database
bull Test Migration processbull Load capacity testing highly recommended
Gain confidence in platform and workload profile Isolate identify fix issues
PLAN DESIGN IMPLEMENT
Stage 4 ndash Deploy amp Stabilise
6 Build amp deploy Production Consolidated SQL Service Consolidatemigrate incrementally
bull Capture baselinebull Add incrementally (ONE at a time)bull Stabilisebull Measure again
Transparent User Experience
7 Measure new Service Compare with lsquooldrsquo Retire old servers
TECHNICAL CONSIDERATIONS
MULTI-INSTANCE SERVERS
Min Max server memoryCPU affinity maskWindows System Resource Manager (WSRM)Failover cluster Possible owners Preferred owners AntiAffinityClassName
SERVER1
BIZSQLSQL1
PLANNING MULTI DATABASES
Resource Governor Min max CPU Min max Memory
Un-managed Worker threads TempDB Plan cache
SERVER1
SQL1
VIRTUALISATION DESIGN
Proper hardware sizing criticalGood storage configuration is critical Use fixed or pass-thru disks (avoid dynamic disks) Avoid thin-provisioning Tune storage configuration
Limitations 4 virtual processor per guest 64 cores in host 64 GB memory in host
x64 benefits are significantAvoid over-committing CPU or memoryStart with single VPU
Recommendations
VIRTUALISATION WITH HIGH AVAILABILITY
Virtual machine failoverHigh Availability regardless of Windows or SQL edition
Live Migration with Hyper-V Uses Failover clustering Requires Win 2008 R2 Single host failover
VIRTUALISATION FOR SITE RESILIENCE
Using virtualisation to provide site resilienceSite-to-site disaster recovery
INTERESTING READS
SQL Server Consolidation Whitepaperhttpwwwmicrosoftcomsqlserver2008enuswhite-papersaspx
SQL Server Virtualisation Whitepaperhttpdownloadmicrosoftcomdownloadd94d948f981-926e-40fa-a026-5bfcf076d9b9SQL2008inHyperV2008docx
Microsoft Assessment and Planning Toolkit httpwwwmicrosoftcomdownloadsdetailsaspxFamilyID=67240b76-3148-4e49-943d-4d9ea7f77730ampdisplaylang=en
Windows System Resource Manager (WSRM)httptechnetmicrosoftcomen-uslibrarycc771218(WS10)aspx
SUMMARY
Plan Design Deliver ConsolidationConstruct Guiding Principles
Identify good candidates for consolidationProviding workload
isolationAn approach to consolidating an estate
HIGH LEVEL PLANNING
Strategy
Motivation for consolidation and end goalsMeasure quantify benefitsEstablish Guiding Principles
People
Potential change in the ownership (DBA Custodianship) of databull Technically Database Ownership (DBO) can be retained
Ongoing support and change managementbull System Administration role change
HIGH LEVEL PLANNING
ProcessAdministrative Operational Performance MonitoringTuning BackupRestore Capacity PlanningMigration and rollback planning
TechnologyCPU memory management IO subsystemWorkload isolationConsolidation ndash name conflicts objects security logins
Management FocusCritical to success
CONSOLIDATION ROADMAP
SQL 2000 2005 amp older
instances
SQL 2008 (2005) Instances
Much More Challenging
One at a time or
en-masse
One at a timeCurrent Environment
ldquoTo Berdquo Environment
bull Monitor behavior
bull Stabilise
Staging Environment
Test amp Production Consolidated
SQL 2008
GUIDING PRINCIPLES
Evaluate Customise and Adopt
Start by consolidating non-mission critical workloadUpgrade to SQL 2008 before consolidating Consolidate similar workloads into single SQL Server instanceAvoid bug fixes during consolidationMaintain transparent user experience Drive standardisation (configuration and operations)
PLANNING DESIGN amp IMPLEMENTATION
PLAN DESIGN IMPLEMENT
Stage 1 ndash Envision1 Current Environment Assessment
Discovery Audit Business Requirements SLA RPO RTO Workload profile transaction volumes processor disk memory SQL Server feature usage Linked servers Extended SP
2 Identify Target Environment amp Develop Consolidation Principles First cut ldquoTo Berdquo environment Discuss gather feedback revise target environment Review financial justification - RoI Develop Consolidation Guiding Principles
PLAN DESIGN IMPLEMENT
Stage 2 ndash Plan amp Design
3 Design lsquoFuturersquo Consolidated Infrastructure Develop design Blueprint Design Review
4 Service User amp Data Migration Planning Migration approach Deployment planning Sequencing of Applications Users Data Design develop migration scripts
PLAN DESIGN IMPLEMENT
Stage 3 ndash Implement
5 Commission consolidated environment for test Test parallel to production Migrate test database
bull Test Migration processbull Load capacity testing highly recommended
Gain confidence in platform and workload profile Isolate identify fix issues
PLAN DESIGN IMPLEMENT
Stage 4 ndash Deploy amp Stabilise
6 Build amp deploy Production Consolidated SQL Service Consolidatemigrate incrementally
bull Capture baselinebull Add incrementally (ONE at a time)bull Stabilisebull Measure again
Transparent User Experience
7 Measure new Service Compare with lsquooldrsquo Retire old servers
TECHNICAL CONSIDERATIONS
MULTI-INSTANCE SERVERS
Min Max server memoryCPU affinity maskWindows System Resource Manager (WSRM)Failover cluster Possible owners Preferred owners AntiAffinityClassName
SERVER1
BIZSQLSQL1
PLANNING MULTI DATABASES
Resource Governor Min max CPU Min max Memory
Un-managed Worker threads TempDB Plan cache
SERVER1
SQL1
VIRTUALISATION DESIGN
Proper hardware sizing criticalGood storage configuration is critical Use fixed or pass-thru disks (avoid dynamic disks) Avoid thin-provisioning Tune storage configuration
Limitations 4 virtual processor per guest 64 cores in host 64 GB memory in host
x64 benefits are significantAvoid over-committing CPU or memoryStart with single VPU
Recommendations
VIRTUALISATION WITH HIGH AVAILABILITY
Virtual machine failoverHigh Availability regardless of Windows or SQL edition
Live Migration with Hyper-V Uses Failover clustering Requires Win 2008 R2 Single host failover
VIRTUALISATION FOR SITE RESILIENCE
Using virtualisation to provide site resilienceSite-to-site disaster recovery
INTERESTING READS
SQL Server Consolidation Whitepaperhttpwwwmicrosoftcomsqlserver2008enuswhite-papersaspx
SQL Server Virtualisation Whitepaperhttpdownloadmicrosoftcomdownloadd94d948f981-926e-40fa-a026-5bfcf076d9b9SQL2008inHyperV2008docx
Microsoft Assessment and Planning Toolkit httpwwwmicrosoftcomdownloadsdetailsaspxFamilyID=67240b76-3148-4e49-943d-4d9ea7f77730ampdisplaylang=en
Windows System Resource Manager (WSRM)httptechnetmicrosoftcomen-uslibrarycc771218(WS10)aspx
SUMMARY
Plan Design Deliver ConsolidationConstruct Guiding Principles
Identify good candidates for consolidationProviding workload
isolationAn approach to consolidating an estate
HIGH LEVEL PLANNING
ProcessAdministrative Operational Performance MonitoringTuning BackupRestore Capacity PlanningMigration and rollback planning
TechnologyCPU memory management IO subsystemWorkload isolationConsolidation ndash name conflicts objects security logins
Management FocusCritical to success
CONSOLIDATION ROADMAP
SQL 2000 2005 amp older
instances
SQL 2008 (2005) Instances
Much More Challenging
One at a time or
en-masse
One at a timeCurrent Environment
ldquoTo Berdquo Environment
bull Monitor behavior
bull Stabilise
Staging Environment
Test amp Production Consolidated
SQL 2008
GUIDING PRINCIPLES
Evaluate Customise and Adopt
Start by consolidating non-mission critical workloadUpgrade to SQL 2008 before consolidating Consolidate similar workloads into single SQL Server instanceAvoid bug fixes during consolidationMaintain transparent user experience Drive standardisation (configuration and operations)
PLANNING DESIGN amp IMPLEMENTATION
PLAN DESIGN IMPLEMENT
Stage 1 ndash Envision1 Current Environment Assessment
Discovery Audit Business Requirements SLA RPO RTO Workload profile transaction volumes processor disk memory SQL Server feature usage Linked servers Extended SP
2 Identify Target Environment amp Develop Consolidation Principles First cut ldquoTo Berdquo environment Discuss gather feedback revise target environment Review financial justification - RoI Develop Consolidation Guiding Principles
PLAN DESIGN IMPLEMENT
Stage 2 ndash Plan amp Design
3 Design lsquoFuturersquo Consolidated Infrastructure Develop design Blueprint Design Review
4 Service User amp Data Migration Planning Migration approach Deployment planning Sequencing of Applications Users Data Design develop migration scripts
PLAN DESIGN IMPLEMENT
Stage 3 ndash Implement
5 Commission consolidated environment for test Test parallel to production Migrate test database
bull Test Migration processbull Load capacity testing highly recommended
Gain confidence in platform and workload profile Isolate identify fix issues
PLAN DESIGN IMPLEMENT
Stage 4 ndash Deploy amp Stabilise
6 Build amp deploy Production Consolidated SQL Service Consolidatemigrate incrementally
bull Capture baselinebull Add incrementally (ONE at a time)bull Stabilisebull Measure again
Transparent User Experience
7 Measure new Service Compare with lsquooldrsquo Retire old servers
TECHNICAL CONSIDERATIONS
MULTI-INSTANCE SERVERS
Min Max server memoryCPU affinity maskWindows System Resource Manager (WSRM)Failover cluster Possible owners Preferred owners AntiAffinityClassName
SERVER1
BIZSQLSQL1
PLANNING MULTI DATABASES
Resource Governor Min max CPU Min max Memory
Un-managed Worker threads TempDB Plan cache
SERVER1
SQL1
VIRTUALISATION DESIGN
Proper hardware sizing criticalGood storage configuration is critical Use fixed or pass-thru disks (avoid dynamic disks) Avoid thin-provisioning Tune storage configuration
Limitations 4 virtual processor per guest 64 cores in host 64 GB memory in host
x64 benefits are significantAvoid over-committing CPU or memoryStart with single VPU
Recommendations
VIRTUALISATION WITH HIGH AVAILABILITY
Virtual machine failoverHigh Availability regardless of Windows or SQL edition
Live Migration with Hyper-V Uses Failover clustering Requires Win 2008 R2 Single host failover
VIRTUALISATION FOR SITE RESILIENCE
Using virtualisation to provide site resilienceSite-to-site disaster recovery
INTERESTING READS
SQL Server Consolidation Whitepaperhttpwwwmicrosoftcomsqlserver2008enuswhite-papersaspx
SQL Server Virtualisation Whitepaperhttpdownloadmicrosoftcomdownloadd94d948f981-926e-40fa-a026-5bfcf076d9b9SQL2008inHyperV2008docx
Microsoft Assessment and Planning Toolkit httpwwwmicrosoftcomdownloadsdetailsaspxFamilyID=67240b76-3148-4e49-943d-4d9ea7f77730ampdisplaylang=en
Windows System Resource Manager (WSRM)httptechnetmicrosoftcomen-uslibrarycc771218(WS10)aspx
SUMMARY
Plan Design Deliver ConsolidationConstruct Guiding Principles
Identify good candidates for consolidationProviding workload
isolationAn approach to consolidating an estate
CONSOLIDATION ROADMAP
SQL 2000 2005 amp older
instances
SQL 2008 (2005) Instances
Much More Challenging
One at a time or
en-masse
One at a timeCurrent Environment
ldquoTo Berdquo Environment
bull Monitor behavior
bull Stabilise
Staging Environment
Test amp Production Consolidated
SQL 2008
GUIDING PRINCIPLES
Evaluate Customise and Adopt
Start by consolidating non-mission critical workloadUpgrade to SQL 2008 before consolidating Consolidate similar workloads into single SQL Server instanceAvoid bug fixes during consolidationMaintain transparent user experience Drive standardisation (configuration and operations)
PLANNING DESIGN amp IMPLEMENTATION
PLAN DESIGN IMPLEMENT
Stage 1 ndash Envision1 Current Environment Assessment
Discovery Audit Business Requirements SLA RPO RTO Workload profile transaction volumes processor disk memory SQL Server feature usage Linked servers Extended SP
2 Identify Target Environment amp Develop Consolidation Principles First cut ldquoTo Berdquo environment Discuss gather feedback revise target environment Review financial justification - RoI Develop Consolidation Guiding Principles
PLAN DESIGN IMPLEMENT
Stage 2 ndash Plan amp Design
3 Design lsquoFuturersquo Consolidated Infrastructure Develop design Blueprint Design Review
4 Service User amp Data Migration Planning Migration approach Deployment planning Sequencing of Applications Users Data Design develop migration scripts
PLAN DESIGN IMPLEMENT
Stage 3 ndash Implement
5 Commission consolidated environment for test Test parallel to production Migrate test database
bull Test Migration processbull Load capacity testing highly recommended
Gain confidence in platform and workload profile Isolate identify fix issues
PLAN DESIGN IMPLEMENT
Stage 4 ndash Deploy amp Stabilise
6 Build amp deploy Production Consolidated SQL Service Consolidatemigrate incrementally
bull Capture baselinebull Add incrementally (ONE at a time)bull Stabilisebull Measure again
Transparent User Experience
7 Measure new Service Compare with lsquooldrsquo Retire old servers
TECHNICAL CONSIDERATIONS
MULTI-INSTANCE SERVERS
Min Max server memoryCPU affinity maskWindows System Resource Manager (WSRM)Failover cluster Possible owners Preferred owners AntiAffinityClassName
SERVER1
BIZSQLSQL1
PLANNING MULTI DATABASES
Resource Governor Min max CPU Min max Memory
Un-managed Worker threads TempDB Plan cache
SERVER1
SQL1
VIRTUALISATION DESIGN
Proper hardware sizing criticalGood storage configuration is critical Use fixed or pass-thru disks (avoid dynamic disks) Avoid thin-provisioning Tune storage configuration
Limitations 4 virtual processor per guest 64 cores in host 64 GB memory in host
x64 benefits are significantAvoid over-committing CPU or memoryStart with single VPU
Recommendations
VIRTUALISATION WITH HIGH AVAILABILITY
Virtual machine failoverHigh Availability regardless of Windows or SQL edition
Live Migration with Hyper-V Uses Failover clustering Requires Win 2008 R2 Single host failover
VIRTUALISATION FOR SITE RESILIENCE
Using virtualisation to provide site resilienceSite-to-site disaster recovery
INTERESTING READS
SQL Server Consolidation Whitepaperhttpwwwmicrosoftcomsqlserver2008enuswhite-papersaspx
SQL Server Virtualisation Whitepaperhttpdownloadmicrosoftcomdownloadd94d948f981-926e-40fa-a026-5bfcf076d9b9SQL2008inHyperV2008docx
Microsoft Assessment and Planning Toolkit httpwwwmicrosoftcomdownloadsdetailsaspxFamilyID=67240b76-3148-4e49-943d-4d9ea7f77730ampdisplaylang=en
Windows System Resource Manager (WSRM)httptechnetmicrosoftcomen-uslibrarycc771218(WS10)aspx
SUMMARY
Plan Design Deliver ConsolidationConstruct Guiding Principles
Identify good candidates for consolidationProviding workload
isolationAn approach to consolidating an estate
GUIDING PRINCIPLES
Evaluate Customise and Adopt
Start by consolidating non-mission critical workloadUpgrade to SQL 2008 before consolidating Consolidate similar workloads into single SQL Server instanceAvoid bug fixes during consolidationMaintain transparent user experience Drive standardisation (configuration and operations)
PLANNING DESIGN amp IMPLEMENTATION
PLAN DESIGN IMPLEMENT
Stage 1 ndash Envision1 Current Environment Assessment
Discovery Audit Business Requirements SLA RPO RTO Workload profile transaction volumes processor disk memory SQL Server feature usage Linked servers Extended SP
2 Identify Target Environment amp Develop Consolidation Principles First cut ldquoTo Berdquo environment Discuss gather feedback revise target environment Review financial justification - RoI Develop Consolidation Guiding Principles
PLAN DESIGN IMPLEMENT
Stage 2 ndash Plan amp Design
3 Design lsquoFuturersquo Consolidated Infrastructure Develop design Blueprint Design Review
4 Service User amp Data Migration Planning Migration approach Deployment planning Sequencing of Applications Users Data Design develop migration scripts
PLAN DESIGN IMPLEMENT
Stage 3 ndash Implement
5 Commission consolidated environment for test Test parallel to production Migrate test database
bull Test Migration processbull Load capacity testing highly recommended
Gain confidence in platform and workload profile Isolate identify fix issues
PLAN DESIGN IMPLEMENT
Stage 4 ndash Deploy amp Stabilise
6 Build amp deploy Production Consolidated SQL Service Consolidatemigrate incrementally
bull Capture baselinebull Add incrementally (ONE at a time)bull Stabilisebull Measure again
Transparent User Experience
7 Measure new Service Compare with lsquooldrsquo Retire old servers
TECHNICAL CONSIDERATIONS
MULTI-INSTANCE SERVERS
Min Max server memoryCPU affinity maskWindows System Resource Manager (WSRM)Failover cluster Possible owners Preferred owners AntiAffinityClassName
SERVER1
BIZSQLSQL1
PLANNING MULTI DATABASES
Resource Governor Min max CPU Min max Memory
Un-managed Worker threads TempDB Plan cache
SERVER1
SQL1
VIRTUALISATION DESIGN
Proper hardware sizing criticalGood storage configuration is critical Use fixed or pass-thru disks (avoid dynamic disks) Avoid thin-provisioning Tune storage configuration
Limitations 4 virtual processor per guest 64 cores in host 64 GB memory in host
x64 benefits are significantAvoid over-committing CPU or memoryStart with single VPU
Recommendations
VIRTUALISATION WITH HIGH AVAILABILITY
Virtual machine failoverHigh Availability regardless of Windows or SQL edition
Live Migration with Hyper-V Uses Failover clustering Requires Win 2008 R2 Single host failover
VIRTUALISATION FOR SITE RESILIENCE
Using virtualisation to provide site resilienceSite-to-site disaster recovery
INTERESTING READS
SQL Server Consolidation Whitepaperhttpwwwmicrosoftcomsqlserver2008enuswhite-papersaspx
SQL Server Virtualisation Whitepaperhttpdownloadmicrosoftcomdownloadd94d948f981-926e-40fa-a026-5bfcf076d9b9SQL2008inHyperV2008docx
Microsoft Assessment and Planning Toolkit httpwwwmicrosoftcomdownloadsdetailsaspxFamilyID=67240b76-3148-4e49-943d-4d9ea7f77730ampdisplaylang=en
Windows System Resource Manager (WSRM)httptechnetmicrosoftcomen-uslibrarycc771218(WS10)aspx
SUMMARY
Plan Design Deliver ConsolidationConstruct Guiding Principles
Identify good candidates for consolidationProviding workload
isolationAn approach to consolidating an estate
PLANNING DESIGN amp IMPLEMENTATION
PLAN DESIGN IMPLEMENT
Stage 1 ndash Envision1 Current Environment Assessment
Discovery Audit Business Requirements SLA RPO RTO Workload profile transaction volumes processor disk memory SQL Server feature usage Linked servers Extended SP
2 Identify Target Environment amp Develop Consolidation Principles First cut ldquoTo Berdquo environment Discuss gather feedback revise target environment Review financial justification - RoI Develop Consolidation Guiding Principles
PLAN DESIGN IMPLEMENT
Stage 2 ndash Plan amp Design
3 Design lsquoFuturersquo Consolidated Infrastructure Develop design Blueprint Design Review
4 Service User amp Data Migration Planning Migration approach Deployment planning Sequencing of Applications Users Data Design develop migration scripts
PLAN DESIGN IMPLEMENT
Stage 3 ndash Implement
5 Commission consolidated environment for test Test parallel to production Migrate test database
bull Test Migration processbull Load capacity testing highly recommended
Gain confidence in platform and workload profile Isolate identify fix issues
PLAN DESIGN IMPLEMENT
Stage 4 ndash Deploy amp Stabilise
6 Build amp deploy Production Consolidated SQL Service Consolidatemigrate incrementally
bull Capture baselinebull Add incrementally (ONE at a time)bull Stabilisebull Measure again
Transparent User Experience
7 Measure new Service Compare with lsquooldrsquo Retire old servers
TECHNICAL CONSIDERATIONS
MULTI-INSTANCE SERVERS
Min Max server memoryCPU affinity maskWindows System Resource Manager (WSRM)Failover cluster Possible owners Preferred owners AntiAffinityClassName
SERVER1
BIZSQLSQL1
PLANNING MULTI DATABASES
Resource Governor Min max CPU Min max Memory
Un-managed Worker threads TempDB Plan cache
SERVER1
SQL1
VIRTUALISATION DESIGN
Proper hardware sizing criticalGood storage configuration is critical Use fixed or pass-thru disks (avoid dynamic disks) Avoid thin-provisioning Tune storage configuration
Limitations 4 virtual processor per guest 64 cores in host 64 GB memory in host
x64 benefits are significantAvoid over-committing CPU or memoryStart with single VPU
Recommendations
VIRTUALISATION WITH HIGH AVAILABILITY
Virtual machine failoverHigh Availability regardless of Windows or SQL edition
Live Migration with Hyper-V Uses Failover clustering Requires Win 2008 R2 Single host failover
VIRTUALISATION FOR SITE RESILIENCE
Using virtualisation to provide site resilienceSite-to-site disaster recovery
INTERESTING READS
SQL Server Consolidation Whitepaperhttpwwwmicrosoftcomsqlserver2008enuswhite-papersaspx
SQL Server Virtualisation Whitepaperhttpdownloadmicrosoftcomdownloadd94d948f981-926e-40fa-a026-5bfcf076d9b9SQL2008inHyperV2008docx
Microsoft Assessment and Planning Toolkit httpwwwmicrosoftcomdownloadsdetailsaspxFamilyID=67240b76-3148-4e49-943d-4d9ea7f77730ampdisplaylang=en
Windows System Resource Manager (WSRM)httptechnetmicrosoftcomen-uslibrarycc771218(WS10)aspx
SUMMARY
Plan Design Deliver ConsolidationConstruct Guiding Principles
Identify good candidates for consolidationProviding workload
isolationAn approach to consolidating an estate
PLAN DESIGN IMPLEMENT
Stage 1 ndash Envision1 Current Environment Assessment
Discovery Audit Business Requirements SLA RPO RTO Workload profile transaction volumes processor disk memory SQL Server feature usage Linked servers Extended SP
2 Identify Target Environment amp Develop Consolidation Principles First cut ldquoTo Berdquo environment Discuss gather feedback revise target environment Review financial justification - RoI Develop Consolidation Guiding Principles
PLAN DESIGN IMPLEMENT
Stage 2 ndash Plan amp Design
3 Design lsquoFuturersquo Consolidated Infrastructure Develop design Blueprint Design Review
4 Service User amp Data Migration Planning Migration approach Deployment planning Sequencing of Applications Users Data Design develop migration scripts
PLAN DESIGN IMPLEMENT
Stage 3 ndash Implement
5 Commission consolidated environment for test Test parallel to production Migrate test database
bull Test Migration processbull Load capacity testing highly recommended
Gain confidence in platform and workload profile Isolate identify fix issues
PLAN DESIGN IMPLEMENT
Stage 4 ndash Deploy amp Stabilise
6 Build amp deploy Production Consolidated SQL Service Consolidatemigrate incrementally
bull Capture baselinebull Add incrementally (ONE at a time)bull Stabilisebull Measure again
Transparent User Experience
7 Measure new Service Compare with lsquooldrsquo Retire old servers
TECHNICAL CONSIDERATIONS
MULTI-INSTANCE SERVERS
Min Max server memoryCPU affinity maskWindows System Resource Manager (WSRM)Failover cluster Possible owners Preferred owners AntiAffinityClassName
SERVER1
BIZSQLSQL1
PLANNING MULTI DATABASES
Resource Governor Min max CPU Min max Memory
Un-managed Worker threads TempDB Plan cache
SERVER1
SQL1
VIRTUALISATION DESIGN
Proper hardware sizing criticalGood storage configuration is critical Use fixed or pass-thru disks (avoid dynamic disks) Avoid thin-provisioning Tune storage configuration
Limitations 4 virtual processor per guest 64 cores in host 64 GB memory in host
x64 benefits are significantAvoid over-committing CPU or memoryStart with single VPU
Recommendations
VIRTUALISATION WITH HIGH AVAILABILITY
Virtual machine failoverHigh Availability regardless of Windows or SQL edition
Live Migration with Hyper-V Uses Failover clustering Requires Win 2008 R2 Single host failover
VIRTUALISATION FOR SITE RESILIENCE
Using virtualisation to provide site resilienceSite-to-site disaster recovery
INTERESTING READS
SQL Server Consolidation Whitepaperhttpwwwmicrosoftcomsqlserver2008enuswhite-papersaspx
SQL Server Virtualisation Whitepaperhttpdownloadmicrosoftcomdownloadd94d948f981-926e-40fa-a026-5bfcf076d9b9SQL2008inHyperV2008docx
Microsoft Assessment and Planning Toolkit httpwwwmicrosoftcomdownloadsdetailsaspxFamilyID=67240b76-3148-4e49-943d-4d9ea7f77730ampdisplaylang=en
Windows System Resource Manager (WSRM)httptechnetmicrosoftcomen-uslibrarycc771218(WS10)aspx
SUMMARY
Plan Design Deliver ConsolidationConstruct Guiding Principles
Identify good candidates for consolidationProviding workload
isolationAn approach to consolidating an estate
PLAN DESIGN IMPLEMENT
Stage 2 ndash Plan amp Design
3 Design lsquoFuturersquo Consolidated Infrastructure Develop design Blueprint Design Review
4 Service User amp Data Migration Planning Migration approach Deployment planning Sequencing of Applications Users Data Design develop migration scripts
PLAN DESIGN IMPLEMENT
Stage 3 ndash Implement
5 Commission consolidated environment for test Test parallel to production Migrate test database
bull Test Migration processbull Load capacity testing highly recommended
Gain confidence in platform and workload profile Isolate identify fix issues
PLAN DESIGN IMPLEMENT
Stage 4 ndash Deploy amp Stabilise
6 Build amp deploy Production Consolidated SQL Service Consolidatemigrate incrementally
bull Capture baselinebull Add incrementally (ONE at a time)bull Stabilisebull Measure again
Transparent User Experience
7 Measure new Service Compare with lsquooldrsquo Retire old servers
TECHNICAL CONSIDERATIONS
MULTI-INSTANCE SERVERS
Min Max server memoryCPU affinity maskWindows System Resource Manager (WSRM)Failover cluster Possible owners Preferred owners AntiAffinityClassName
SERVER1
BIZSQLSQL1
PLANNING MULTI DATABASES
Resource Governor Min max CPU Min max Memory
Un-managed Worker threads TempDB Plan cache
SERVER1
SQL1
VIRTUALISATION DESIGN
Proper hardware sizing criticalGood storage configuration is critical Use fixed or pass-thru disks (avoid dynamic disks) Avoid thin-provisioning Tune storage configuration
Limitations 4 virtual processor per guest 64 cores in host 64 GB memory in host
x64 benefits are significantAvoid over-committing CPU or memoryStart with single VPU
Recommendations
VIRTUALISATION WITH HIGH AVAILABILITY
Virtual machine failoverHigh Availability regardless of Windows or SQL edition
Live Migration with Hyper-V Uses Failover clustering Requires Win 2008 R2 Single host failover
VIRTUALISATION FOR SITE RESILIENCE
Using virtualisation to provide site resilienceSite-to-site disaster recovery
INTERESTING READS
SQL Server Consolidation Whitepaperhttpwwwmicrosoftcomsqlserver2008enuswhite-papersaspx
SQL Server Virtualisation Whitepaperhttpdownloadmicrosoftcomdownloadd94d948f981-926e-40fa-a026-5bfcf076d9b9SQL2008inHyperV2008docx
Microsoft Assessment and Planning Toolkit httpwwwmicrosoftcomdownloadsdetailsaspxFamilyID=67240b76-3148-4e49-943d-4d9ea7f77730ampdisplaylang=en
Windows System Resource Manager (WSRM)httptechnetmicrosoftcomen-uslibrarycc771218(WS10)aspx
SUMMARY
Plan Design Deliver ConsolidationConstruct Guiding Principles
Identify good candidates for consolidationProviding workload
isolationAn approach to consolidating an estate
PLAN DESIGN IMPLEMENT
Stage 3 ndash Implement
5 Commission consolidated environment for test Test parallel to production Migrate test database
bull Test Migration processbull Load capacity testing highly recommended
Gain confidence in platform and workload profile Isolate identify fix issues
PLAN DESIGN IMPLEMENT
Stage 4 ndash Deploy amp Stabilise
6 Build amp deploy Production Consolidated SQL Service Consolidatemigrate incrementally
bull Capture baselinebull Add incrementally (ONE at a time)bull Stabilisebull Measure again
Transparent User Experience
7 Measure new Service Compare with lsquooldrsquo Retire old servers
TECHNICAL CONSIDERATIONS
MULTI-INSTANCE SERVERS
Min Max server memoryCPU affinity maskWindows System Resource Manager (WSRM)Failover cluster Possible owners Preferred owners AntiAffinityClassName
SERVER1
BIZSQLSQL1
PLANNING MULTI DATABASES
Resource Governor Min max CPU Min max Memory
Un-managed Worker threads TempDB Plan cache
SERVER1
SQL1
VIRTUALISATION DESIGN
Proper hardware sizing criticalGood storage configuration is critical Use fixed or pass-thru disks (avoid dynamic disks) Avoid thin-provisioning Tune storage configuration
Limitations 4 virtual processor per guest 64 cores in host 64 GB memory in host
x64 benefits are significantAvoid over-committing CPU or memoryStart with single VPU
Recommendations
VIRTUALISATION WITH HIGH AVAILABILITY
Virtual machine failoverHigh Availability regardless of Windows or SQL edition
Live Migration with Hyper-V Uses Failover clustering Requires Win 2008 R2 Single host failover
VIRTUALISATION FOR SITE RESILIENCE
Using virtualisation to provide site resilienceSite-to-site disaster recovery
INTERESTING READS
SQL Server Consolidation Whitepaperhttpwwwmicrosoftcomsqlserver2008enuswhite-papersaspx
SQL Server Virtualisation Whitepaperhttpdownloadmicrosoftcomdownloadd94d948f981-926e-40fa-a026-5bfcf076d9b9SQL2008inHyperV2008docx
Microsoft Assessment and Planning Toolkit httpwwwmicrosoftcomdownloadsdetailsaspxFamilyID=67240b76-3148-4e49-943d-4d9ea7f77730ampdisplaylang=en
Windows System Resource Manager (WSRM)httptechnetmicrosoftcomen-uslibrarycc771218(WS10)aspx
SUMMARY
Plan Design Deliver ConsolidationConstruct Guiding Principles
Identify good candidates for consolidationProviding workload
isolationAn approach to consolidating an estate
PLAN DESIGN IMPLEMENT
Stage 4 ndash Deploy amp Stabilise
6 Build amp deploy Production Consolidated SQL Service Consolidatemigrate incrementally
bull Capture baselinebull Add incrementally (ONE at a time)bull Stabilisebull Measure again
Transparent User Experience
7 Measure new Service Compare with lsquooldrsquo Retire old servers
TECHNICAL CONSIDERATIONS
MULTI-INSTANCE SERVERS
Min Max server memoryCPU affinity maskWindows System Resource Manager (WSRM)Failover cluster Possible owners Preferred owners AntiAffinityClassName
SERVER1
BIZSQLSQL1
PLANNING MULTI DATABASES
Resource Governor Min max CPU Min max Memory
Un-managed Worker threads TempDB Plan cache
SERVER1
SQL1
VIRTUALISATION DESIGN
Proper hardware sizing criticalGood storage configuration is critical Use fixed or pass-thru disks (avoid dynamic disks) Avoid thin-provisioning Tune storage configuration
Limitations 4 virtual processor per guest 64 cores in host 64 GB memory in host
x64 benefits are significantAvoid over-committing CPU or memoryStart with single VPU
Recommendations
VIRTUALISATION WITH HIGH AVAILABILITY
Virtual machine failoverHigh Availability regardless of Windows or SQL edition
Live Migration with Hyper-V Uses Failover clustering Requires Win 2008 R2 Single host failover
VIRTUALISATION FOR SITE RESILIENCE
Using virtualisation to provide site resilienceSite-to-site disaster recovery
INTERESTING READS
SQL Server Consolidation Whitepaperhttpwwwmicrosoftcomsqlserver2008enuswhite-papersaspx
SQL Server Virtualisation Whitepaperhttpdownloadmicrosoftcomdownloadd94d948f981-926e-40fa-a026-5bfcf076d9b9SQL2008inHyperV2008docx
Microsoft Assessment and Planning Toolkit httpwwwmicrosoftcomdownloadsdetailsaspxFamilyID=67240b76-3148-4e49-943d-4d9ea7f77730ampdisplaylang=en
Windows System Resource Manager (WSRM)httptechnetmicrosoftcomen-uslibrarycc771218(WS10)aspx
SUMMARY
Plan Design Deliver ConsolidationConstruct Guiding Principles
Identify good candidates for consolidationProviding workload
isolationAn approach to consolidating an estate
TECHNICAL CONSIDERATIONS
MULTI-INSTANCE SERVERS
Min Max server memoryCPU affinity maskWindows System Resource Manager (WSRM)Failover cluster Possible owners Preferred owners AntiAffinityClassName
SERVER1
BIZSQLSQL1
PLANNING MULTI DATABASES
Resource Governor Min max CPU Min max Memory
Un-managed Worker threads TempDB Plan cache
SERVER1
SQL1
VIRTUALISATION DESIGN
Proper hardware sizing criticalGood storage configuration is critical Use fixed or pass-thru disks (avoid dynamic disks) Avoid thin-provisioning Tune storage configuration
Limitations 4 virtual processor per guest 64 cores in host 64 GB memory in host
x64 benefits are significantAvoid over-committing CPU or memoryStart with single VPU
Recommendations
VIRTUALISATION WITH HIGH AVAILABILITY
Virtual machine failoverHigh Availability regardless of Windows or SQL edition
Live Migration with Hyper-V Uses Failover clustering Requires Win 2008 R2 Single host failover
VIRTUALISATION FOR SITE RESILIENCE
Using virtualisation to provide site resilienceSite-to-site disaster recovery
INTERESTING READS
SQL Server Consolidation Whitepaperhttpwwwmicrosoftcomsqlserver2008enuswhite-papersaspx
SQL Server Virtualisation Whitepaperhttpdownloadmicrosoftcomdownloadd94d948f981-926e-40fa-a026-5bfcf076d9b9SQL2008inHyperV2008docx
Microsoft Assessment and Planning Toolkit httpwwwmicrosoftcomdownloadsdetailsaspxFamilyID=67240b76-3148-4e49-943d-4d9ea7f77730ampdisplaylang=en
Windows System Resource Manager (WSRM)httptechnetmicrosoftcomen-uslibrarycc771218(WS10)aspx
SUMMARY
Plan Design Deliver ConsolidationConstruct Guiding Principles
Identify good candidates for consolidationProviding workload
isolationAn approach to consolidating an estate
MULTI-INSTANCE SERVERS
Min Max server memoryCPU affinity maskWindows System Resource Manager (WSRM)Failover cluster Possible owners Preferred owners AntiAffinityClassName
SERVER1
BIZSQLSQL1
PLANNING MULTI DATABASES
Resource Governor Min max CPU Min max Memory
Un-managed Worker threads TempDB Plan cache
SERVER1
SQL1
VIRTUALISATION DESIGN
Proper hardware sizing criticalGood storage configuration is critical Use fixed or pass-thru disks (avoid dynamic disks) Avoid thin-provisioning Tune storage configuration
Limitations 4 virtual processor per guest 64 cores in host 64 GB memory in host
x64 benefits are significantAvoid over-committing CPU or memoryStart with single VPU
Recommendations
VIRTUALISATION WITH HIGH AVAILABILITY
Virtual machine failoverHigh Availability regardless of Windows or SQL edition
Live Migration with Hyper-V Uses Failover clustering Requires Win 2008 R2 Single host failover
VIRTUALISATION FOR SITE RESILIENCE
Using virtualisation to provide site resilienceSite-to-site disaster recovery
INTERESTING READS
SQL Server Consolidation Whitepaperhttpwwwmicrosoftcomsqlserver2008enuswhite-papersaspx
SQL Server Virtualisation Whitepaperhttpdownloadmicrosoftcomdownloadd94d948f981-926e-40fa-a026-5bfcf076d9b9SQL2008inHyperV2008docx
Microsoft Assessment and Planning Toolkit httpwwwmicrosoftcomdownloadsdetailsaspxFamilyID=67240b76-3148-4e49-943d-4d9ea7f77730ampdisplaylang=en
Windows System Resource Manager (WSRM)httptechnetmicrosoftcomen-uslibrarycc771218(WS10)aspx
SUMMARY
Plan Design Deliver ConsolidationConstruct Guiding Principles
Identify good candidates for consolidationProviding workload
isolationAn approach to consolidating an estate
PLANNING MULTI DATABASES
Resource Governor Min max CPU Min max Memory
Un-managed Worker threads TempDB Plan cache
SERVER1
SQL1
VIRTUALISATION DESIGN
Proper hardware sizing criticalGood storage configuration is critical Use fixed or pass-thru disks (avoid dynamic disks) Avoid thin-provisioning Tune storage configuration
Limitations 4 virtual processor per guest 64 cores in host 64 GB memory in host
x64 benefits are significantAvoid over-committing CPU or memoryStart with single VPU
Recommendations
VIRTUALISATION WITH HIGH AVAILABILITY
Virtual machine failoverHigh Availability regardless of Windows or SQL edition
Live Migration with Hyper-V Uses Failover clustering Requires Win 2008 R2 Single host failover
VIRTUALISATION FOR SITE RESILIENCE
Using virtualisation to provide site resilienceSite-to-site disaster recovery
INTERESTING READS
SQL Server Consolidation Whitepaperhttpwwwmicrosoftcomsqlserver2008enuswhite-papersaspx
SQL Server Virtualisation Whitepaperhttpdownloadmicrosoftcomdownloadd94d948f981-926e-40fa-a026-5bfcf076d9b9SQL2008inHyperV2008docx
Microsoft Assessment and Planning Toolkit httpwwwmicrosoftcomdownloadsdetailsaspxFamilyID=67240b76-3148-4e49-943d-4d9ea7f77730ampdisplaylang=en
Windows System Resource Manager (WSRM)httptechnetmicrosoftcomen-uslibrarycc771218(WS10)aspx
SUMMARY
Plan Design Deliver ConsolidationConstruct Guiding Principles
Identify good candidates for consolidationProviding workload
isolationAn approach to consolidating an estate
VIRTUALISATION DESIGN
Proper hardware sizing criticalGood storage configuration is critical Use fixed or pass-thru disks (avoid dynamic disks) Avoid thin-provisioning Tune storage configuration
Limitations 4 virtual processor per guest 64 cores in host 64 GB memory in host
x64 benefits are significantAvoid over-committing CPU or memoryStart with single VPU
Recommendations
VIRTUALISATION WITH HIGH AVAILABILITY
Virtual machine failoverHigh Availability regardless of Windows or SQL edition
Live Migration with Hyper-V Uses Failover clustering Requires Win 2008 R2 Single host failover
VIRTUALISATION FOR SITE RESILIENCE
Using virtualisation to provide site resilienceSite-to-site disaster recovery
INTERESTING READS
SQL Server Consolidation Whitepaperhttpwwwmicrosoftcomsqlserver2008enuswhite-papersaspx
SQL Server Virtualisation Whitepaperhttpdownloadmicrosoftcomdownloadd94d948f981-926e-40fa-a026-5bfcf076d9b9SQL2008inHyperV2008docx
Microsoft Assessment and Planning Toolkit httpwwwmicrosoftcomdownloadsdetailsaspxFamilyID=67240b76-3148-4e49-943d-4d9ea7f77730ampdisplaylang=en
Windows System Resource Manager (WSRM)httptechnetmicrosoftcomen-uslibrarycc771218(WS10)aspx
SUMMARY
Plan Design Deliver ConsolidationConstruct Guiding Principles
Identify good candidates for consolidationProviding workload
isolationAn approach to consolidating an estate
VIRTUALISATION WITH HIGH AVAILABILITY
Virtual machine failoverHigh Availability regardless of Windows or SQL edition
Live Migration with Hyper-V Uses Failover clustering Requires Win 2008 R2 Single host failover
VIRTUALISATION FOR SITE RESILIENCE
Using virtualisation to provide site resilienceSite-to-site disaster recovery
INTERESTING READS
SQL Server Consolidation Whitepaperhttpwwwmicrosoftcomsqlserver2008enuswhite-papersaspx
SQL Server Virtualisation Whitepaperhttpdownloadmicrosoftcomdownloadd94d948f981-926e-40fa-a026-5bfcf076d9b9SQL2008inHyperV2008docx
Microsoft Assessment and Planning Toolkit httpwwwmicrosoftcomdownloadsdetailsaspxFamilyID=67240b76-3148-4e49-943d-4d9ea7f77730ampdisplaylang=en
Windows System Resource Manager (WSRM)httptechnetmicrosoftcomen-uslibrarycc771218(WS10)aspx
SUMMARY
Plan Design Deliver ConsolidationConstruct Guiding Principles
Identify good candidates for consolidationProviding workload
isolationAn approach to consolidating an estate
VIRTUALISATION FOR SITE RESILIENCE
Using virtualisation to provide site resilienceSite-to-site disaster recovery
INTERESTING READS
SQL Server Consolidation Whitepaperhttpwwwmicrosoftcomsqlserver2008enuswhite-papersaspx
SQL Server Virtualisation Whitepaperhttpdownloadmicrosoftcomdownloadd94d948f981-926e-40fa-a026-5bfcf076d9b9SQL2008inHyperV2008docx
Microsoft Assessment and Planning Toolkit httpwwwmicrosoftcomdownloadsdetailsaspxFamilyID=67240b76-3148-4e49-943d-4d9ea7f77730ampdisplaylang=en
Windows System Resource Manager (WSRM)httptechnetmicrosoftcomen-uslibrarycc771218(WS10)aspx
SUMMARY
Plan Design Deliver ConsolidationConstruct Guiding Principles
Identify good candidates for consolidationProviding workload
isolationAn approach to consolidating an estate
INTERESTING READS
SQL Server Consolidation Whitepaperhttpwwwmicrosoftcomsqlserver2008enuswhite-papersaspx
SQL Server Virtualisation Whitepaperhttpdownloadmicrosoftcomdownloadd94d948f981-926e-40fa-a026-5bfcf076d9b9SQL2008inHyperV2008docx
Microsoft Assessment and Planning Toolkit httpwwwmicrosoftcomdownloadsdetailsaspxFamilyID=67240b76-3148-4e49-943d-4d9ea7f77730ampdisplaylang=en
Windows System Resource Manager (WSRM)httptechnetmicrosoftcomen-uslibrarycc771218(WS10)aspx
SUMMARY
Plan Design Deliver ConsolidationConstruct Guiding Principles
Identify good candidates for consolidationProviding workload
isolationAn approach to consolidating an estate
SUMMARY
Plan Design Deliver ConsolidationConstruct Guiding Principles
Identify good candidates for consolidationProviding workload
isolationAn approach to consolidating an estate