Reduce your cost and improve your agility withSQL Server Consolidation

Agenda

• The Trend Towards Consolidation

• Choosing a Data Platform

• Consolidating with SQL Server 2008 R2

2

• Resources

The Trend Towards

Consolidation

3

What Is Consolidation?

Reduce the number of servers in the enterprise and

optimize utilization of hardware resources

Combine applications from multiple underutilized servers to fewer servers

The Trend Towards Consolidation

Forces Driving Consolidation

Cost

• Reduced hardware • Reduce power and cooling

• Lower cooling requirements

• Reduced data center space

• Lower license• Greater efficiency of resource utilization

• Lower administrative

Control

• Greater agility and responsive to business

• Better SLAs• Improved compliance management through reduced surface area

Consistency

• Standardize platform• Easier integration• Fewer management points

The Trend Towards Consolidation

Key Enablers

Software Advances

VirtualizationImproved Bandwidth

Hardware Advances

•Increased processing power •Decreased cost•Storage consolidation (Use of SAN and NAS)

•Improved performance, availability, manageability, and reliability

•Improved server software isolation for application co-existence

•More reliable, faster network reduces need for local servers •Advance, Hypervisor based

virtualization such as Hyper-V

The Trend Towards Consolidation

CLOSE TO 60% COMPLETED OR IN PROGRESS WHILE 36% ARE

CONSIDERING

7

Large Enterprises and ConsolidationThe Trend Towards Consolidation

4%

36%

35%

24%Investigating Consolida-tion

Considering Consolida-tion

Executing Consolidation

Completed Consolida-tion

Base: 246 IT executives and managers at US enterprises(percentages may not total 100 because of rounding) - June 2008 “The Forrester Wave™: IT Consolidation Consultancies, Q2 2008”

Choosing a Data Platform

9

Cost of ownership

Business value

Product roadmap

Virtualization support

Ease of standardizatio

n

Server Consolidation ConsiderationsChoosing a Data Platform

SQL Server 2008 R2 TCOChoosing a Data Platform

Low cost of ownership

• Licensing cost• Complexity and ease of set-up• Support cost• Maintenance cost• Use of low cost commodity hardware• Upgrade cost (SA, EA, APA)• Availability of skilled IT staff• Security breach cost (Highly secured)• Training cost• Integration cost

• Total cost of ownership (TCO) for storage at the low end of the industry average scale: $15 to $30 per gigabyte

• 3-year, risk-adjusted Return on Investment (ROI) of 162% with a payback period of six months after upgrading to SQL Server 2008

Total Economic Impact Of SQL Server 2008 Upgrade

SQL Server 2008 R2 Business ValueChoosing a Data Platform

Out of the box capabilities

• Enterprise Class• Performance & Scalability• Security• Manageability• HA• Virtualization

• Full BI platform• ETL, Data Warehousing, OLAP, Data Mining,

Reporting

• Beyond Relational• XML• User defined data types• Spatial

13

SQL 6.01995

SQL 7.01998

SQL 20002000

SQL 20052005

SQL 20082008

SQL 6.51996

SQL CE2000

64-bit2001

From: Deskside servers

To: Cell phone to Scale-Out Utility to Cloud

From: Tables and BLOBs

To: Objects, Places, Documents, XML, Cubes, …From: CRUD, Backup/Restore

To: Analyze, Synchronize,Integrate, Mine, Extend, …

Small Server

Desktop to SMP (New Architecture)

SQL-CE Device and Desktop

64-bit Megaserver +

Relational

OLAP and ETL

XML (SQL-XML)XML

Objects

Files

Spatial

CLR Functions,Procedures in DBMS Engine

EnterpriseClass ETL

Backup/Restore

Data Mining

Managed Reporting

Replication

XQuery

Ente

rpri

seD

ata

Pla

tform

Pla

tform

for

all

Data

Dynam

ic

Develo

pm

ent

Choosing a Data PlatformPe

rvasi

ve

Insi

ght

From: BI as a specialization

To: BI for everyone

Data Warehousing

BLOB

Ad-hoc Reporting

DW Scale

Data Profiling

Data Visualizations

VS Integration

KPIs

Multiple sources Office Integration

Scripting GUIManagement Studio

Policy-Based Management

Scale-up with>64 Support

Log Shipping Failover ClusteringDatabaseMirroring

* Not a complete list of product release features. Microsoft Confidential—Preliminary Information Subject to Change

Partitioning

ADO.NET

Entity Framework

ADO.NET Data Services

ODBC

OLE DB

SQL 2008 R2SQL Madison*

Auditing

Multi Server Management

On-premiseOff-premise

Massively Scale-out DW

Self-ServiceBI

Product roadmap -Proven past and Promising future

SQL Server 2008 R2 and Virtualization

Virtualization Advantages

Choosing a Data Platform

• Licensing advantages

• Unlimited Virtualization licensing

• Application license mobility

• Proven performance/throughput

• Virtual machine agility

• SC-VMM enable movement of a database server VM from

one physical server to another

• Sysprep

• Simplified data recovery (Hyper-V VHD back-up)

• High Availability with Live Migration, & Guest

Clustering

StandardizationChoosing a Data Platform

Standardization Advantages

• Scales across all areas of business

• OLTPBI/OLAP/DSSWeb

• Small Extremely large Servers

• X86-IA64

• 32 and 64 bit

• Migrate data across the enterprise

• Connect to a wide range of data

sources

• SQL Server

• Oracle

• DB2

• Teradata

Consolidation with SQL Server 2008 R2

Reduce

Cap

-Ex

Reduce

Op-E

xA

gile

IT

Choosing the Right Consolidation Approach

EVALUATE KEY PARAMETERS FOR YOUR ENVIRONMENT

ISOLATION BETWEEN APPS

Security isolation Predictable Performance: Resource isolation

HA: Failure isolation

DENSITY OF APPS

Performance: Resource utilization efficiency

Manageability Impact HA: mitigating single point of

failure

TIME TO MARKET

How long does it take to

consolidate?

Can my solution Scale?

Comparing Consolidation Approaches

VIRTUALIZATION

INSTANCE DATABASE

Security

Resource Management

Density

Migration

High Availability

KEY Best Better Good

Consolidating with SQL Server 2008Server Consolidation Options

Multiple Databases

Consolidating with SQL Server 2008Server Consolidation Options

Multiple Instances

Consolidating with SQL Server 2008 R2

Enterprise Manageability

Policy Based Management

Performance Data Collection

21

Management

• Utility Control Point

• SQL Server Management Studio

• SQL Server Agent

• Central Management Servers

• PowerShell

• Data Tier Application Component

• Define configuration policies on one instance, and apply to many instances

• Evaluate policies to monitor or prevent non-compliance

• Create a central management data warehouse

• Upload data from target servers at scheduled intervals

• View consolidated reports from management data warehouse

Consolidating with SQL Server 2008 R2

Server Clustering Database Mirroring Peer-to-Peer Replication

22

High Availability

• Failover at the instance-level

• Cluster up to 16 nodes with Enterprise Edition

• 2 nodes with Standard Edition

• Failover at the database level

• Enhancements in SQL Server 2008

• Log stream compression

• Automatic recovery of corrupted pages

• Replicate data between distributed instances

• Available only in Enterprise Edition

• Enhancements in SQL Server 2008

• Simplified configuration and management

• Add new nodes without interruption

SecurityIntegrity of consolidated database

Consolidating with SQL Server 2008 R2

• 3-levels of application isolation

• Database (User)

• SQL Server Instance (Login)

• Server (physical or virtual) (Windows Account)

• Transparent Data Encryption

• Data is stored in an encrypted form

• No application changes required

• Enterprise Key Management

• Integrate SQL Server encryption into your enterprise

key management infrastructure

Data and Backup Compression

• Reduce data storage

requirements

• Benefit from increased

performance through reduced

I/O

• Reduce backup storage and

window for backup

• Unicode compression

Reduce Storage RequirementsConsolidating with SQL Server 2008 R2

“Our initial testing shows we’ll see 50 percent to 60 percent data compression using SQL Server 2008...we will also benefit from faster query performance”

Mazal Tuchler, BI Manager, Clalit Health Services

Manage Workloads PredictablyResource Governor

Consolidating with SQL Server 2008 R2

• Manage resource contention

proactively for predictable

performance

• Prioritize important workloads by

defining application pools

• By application, user, database,

etc.

• Consolidate without impacting

mission-critical applications

DB1 DB2 DB3

High-Importance Application Pool

• Min memory: 20%• Max memory: 90%• Max CPU: 90%

Low-Importance Application Pool

• Min memory: 10%• Max memory: 30%• Max CPU: 10%

“We deal with a lot of large data feeds-both coming from manufacturers as data updates, and going out to our subscribers. Resource Governor allows us to control the percent of total resources any operation can consume so that they don’t adversely impact our real-time data access.”

Michael Steineke, Vice President, Information Technology, Edgenet

SQL Server 2008 R2 Support for Virtualization

n

Consolidating with SQL Server 2008Server Consolidation Options

Virtualization

High Availability with Guest Clustering Using iSCSI

Guest Cluster

Guest Cluster

1 2

VM

Redundant Paths to storage

FAULT TOLERANCE BOTH AT APPLICATION AND HOST

MANAGEMENT EFFICIENCY BASED ON SQL SERVER® AND SYSTEM CENTER MANAGEMENT TOOLS

USES WINDOWS FAILOVER CLUSTER

VHDs FOR DISASTER RECOVERY

Shared StorageiSCSI

High Availability with Live Migration

1 2

VM

NO LOSS OF SERVICE

Shared StorageiSCSI, SAS, Fibre

Host cluster

LiveMigration

AVAILABILITY WITH LOWER COMPLEXITY

MANAGE LOADS ON VMS ACROSS PHYSICAL MACHINE

EASIER MANAGEMENT THROUGH SYSTEM CENTER VMM

SQL Server Performance: SLAT Impact

1VM 2VM 3VM 4VM 5VM 6VM 7VM 8VM0

10

20

30

40

50

60

70

80

0

500

1000

1500

2000

2500

3000

3500

Batch req/sec %CPU Relative Throughput

VIRTUAL INSTANCES SCALABILITY% CPU

Throughput(Batch requests/sec)

Relative Throughput for Windows Server 2008

CPU over-commit

Almost Linear ScaleNo CPU over-commit

• OS: Microsoft® Windows Server® 2008 R2 Hyper-V™• Hardware:

• HP DL585 (16 core) with SLAT • HP EVA 8000 storage

• Virtual Machines: 4 virtual processors and 7 GB RAM per virtual machine; Fixed size VHD

CONFIGURATION

HeavyLoad

Moderate

Load

LowLoad

• Increased throughput with consolidation

• Near linear scale in throughput with no CPU over-commit

• Improved performance with Windows Server 2008 R2 and SLAT processor architecture

RESULTS:

Creating and managing Virtual Machines

• Centralized virtual machine deployment and management for Hyper-V, Virtual Server, and VMware ESX servers

• Intelligent placement of Virtual Machines• Fast and reliable P2V and V2V conversion• Comprehensive application and service-level monitoring with Operations

Manager• Integrated Performance and Resource Optmization (PRO) of VMs

MAXIMIZE RESOURCES

• Rapid provisioning of new virtual machines with templates• Centralized library of infrastructure components• Leverage and extend existing storage infrastructure and clusters• Allow for delegated management and access of VMs

INCREASE AGILITY

• Familiar interface, common foundation • Monitor physical and virtual machines from one console • Fully scriptable using Windows PowerShell

LEVERAGE SKILLS

Best Practices and Recommendations

• When compared against native the same throughput can be achieved within a guest VM at a cost of slightly increased CPU utilization

• Hyper-V benefits from newer generation of processor architecture (SLAT, Snoop filter)

• Assuming limitations of Guest VM meet requirements of the workload.• Proper hardware sizing is critical to SQL Server performance • Test/Monitor your workloads

RUNNING SQL SERVER WORKLOADS WITHIN HYPER-V GUEST VM’S IS A GOOD OPTION FOR PRODUCTION

ENVIRONMENT

• May introduce noticeable performance overhead when all workloads are busy

CPU RESOURCES OVER COMMIT ON CASE BY CASE BASIS FOR HIGHER

DENSITY

Consolidation Using Windows & SQL Server 2008 R2®

sysprep SQL setup Data Tier App

Utility Control Point and Managed Instances

>64 logical processors (Windows Server & SQL) 2008 R2

New in SQL 2008 R2®

Resource Governor

Windows Server Resource Manager (WSRM)

Microsoft Assessment and Planning (MAP)

failover clusterin guest VMs

System Center VM Manager

Hyper-VLive Migration

INSTANCESVIRTUAL

MACHINESHIGHER

ISOLATIONHIGHER DENSITY

LOWER ISOLATION

DATABASES

LOWER DENSITY

Utility Control Point (UCP)

• Simple to setup and use

• Central view over managed

instances

• Central point for policy

evaluation

• Central collection point for

resource utilization metrics

SQ

L01 Managed

Instances

UCP

SQ

L04

UCP

SQ

L05

SQ

L03

SQ

L02

DBA

Management Studio

Key Concept - Data Tier Application

• Unit of deployment for T-SQL apps• Contains developer intent as policies• A definition of all the app’s parts• Can Install, Uninstall, and Upgrade

Unit o

f Deplo

ym

ent

Unit o

f Managem

ent

DATA TIER APPLICATION (DAC)

• Unit of management for a DAC• Namespace and resource isolation

DEPLOYED DATA TIER APPLICATION

DATA TIER APPLICATION

Schema

Extra Files

Policies

DATA TIER APPLICATION

Schema

Properties & Metadata

Deploy

$0$2,000,000$4,000,000$6,000,000$8,000,000

$10,000,000$12,000,000$14,000,000$16,000,000$18,000,000$20,000,000

Case Study - Microsoft IT ConsolidationOperational Results

ConsolidatedLegacy

ANNUAL OPERATING COST AT 6:1 CONSOLIDATION

ConsolidatedLegacy

ANNUAL RECYCLE COST AT 6:1 CONSOLIDATION

ConsolidatedLegacy

POWER AND COOLING AT 6:1 CONSOLIDATION

$0

$10,000

$20,000

$30,000

$40,000

$50,000

$60,000

0

500,000

1,000,000

1,500,000

2,000,000

2,500,000

3,000,000

3,500,000

4,000,000

How to ConsolidateConsolidation Resources

Links and Artifacts

• SQL Server Consolidation Guidance

• SQL Server Consolidation

• Server Consolidation Whitepaper

• Best practices on virtualization

• Green IT: SQL Server Consolidation in Microsoft

© 2009 Microsoft Corporation. All rights reserved.This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

Appendix

SM

PN

UM

A

Consolidation Hardware – NUMA & 64bit

Front side bus contention increases w/ higher #CPUs

Memory

CPU 0 CPU 1 CPU 2 CPU 3 CPU 4 CPU 5 CPU 6 CPU 7

NUMA NODE 0

Local Memory Access

Foreign Memory

Access 4x local

CPU 0

CPU 1

CPU 2

CPU 3

NUMA NODE 1

Local Memory Access

MemoryMemory

CPU 4

CPU 5

CPU 6

CPU 7

NUMA Node isolation presents inherent & significant advantages to software that is designed to take advantage of locality

Microsoft HyperV localizes VM resource utilization to a NUMA boundary

64bit allows significantly more addressable space than 32bit

Guest Physical Memory Pages

GUEST PHYSICAL VIEW

Consolidation Hardware – hardware assists

• With Virtualization an additional level of mapping is required in address translation

• Second Level Address Translation (SLAT) - 2nd generation virtualization technology in Intel VT-x with EPT and AMD –V with NPT chips accelerate VM performance to be almost on par with bare metal for common workloads

• Continuing innovations in hardware assists – Device and IO virtualization

THE VIRTUAL MACHINE VIEW

Hyper Visor

Physical Memory Pages

HOST PHYSICAL / REAL VIEW

VIRTUAL MACHINE 1

VIRTUAL MACHINE 2

VIRTUAL MACHINE 3

Operating System

Guest Physical Memory Pages

GUEST PHYSICAL VIEW

Guest Physical Memory Pages

GUEST PHYSICAL VIEW

SQL Server

SQL Agent

Process 1 Process 2

Process 4

Process 7

Operating System

SQL Server

SQL Agent

Process 1 Process 2

Process 4

Process 7

Operating System

SQL Server

SQL Agent

Process 1 Process 2

Process 4

Process 7

Operating System

Consolidation Hardware – Snoop Filtering

C0 C1 C2 C3 MCH0 C4 C5 C6 C7 MCH1

NUMA NODE 0

CPU 0

CPU 1

CPU 2

CPU 3

NUMA NODE 1

MemoryMemory

CPU 4

CPU 5

CPU 6

CPU 7

FETCH ADDR (FIRST TIME)

1) Issue Fetch to Memory Controller Hub (MCH)

2) Snoop local caches

3) Caches respond

4) Snoop foreign caches

5) Caches respond

6) Get data from memory controller

MEM

ORY

Consolidation Hardware – Snoop Filtering

C0 C1 C2 C3 MCH0 C4 C5 C6 C7 MCH1

NUMA NODE 0

CPU 0

CPU 1

CPU 2

CPU 3

NUMA NODE 1

MemoryMemory

CPU 4

CPU 5

CPU 6

CPU 7

FETCH ADDR (FIRST TIME)

1) Issue Fetch to Memory Controller Hub (MCH)

2) Check local snoop filter

3) Check foreign snoop filter

4) Get data from memory controller

MEM

ORY

SNOOP FILTER REDUCES INTERNODE TRAFFIC