REQUIRED 9S & PROTECTION

Mission Critical Confidence

THE FANTASTIC 12 OF 2012

4 3 2 1

11 12 10 9

8 5 7 6

SQL SERVER DELIVERS REQUIRED 9S MAXIMIZE UPTIME FOR MISSION CRITICAL APPLICATIONS

ALWAYSON AVAILABILITY GROUPS

EXAMPLE HA/DR TOPOLOGY

BENEFITS

*Database backup is copy-only type, Log backup is regular. See http://msdn.microsoft.com/en-us/library/hh245119.aspx

Seamless connectivity to primary through Listener Virtual Network Name

1 Virtual IP per subnet

Cluster resource

Part of AG resource group

Fails over with AG (binds to network interface)

AVAILABILITY GROUP REPLACES DB MIRRORING

NEW TOPOLOGY BENEFITS

CONSIDERATIONS FOR AVAILABILITY GROUPS

CLUSTER CONSIDERATIONS

Cluster Members must be in same Windows domain or trusted domains

Cluster needs quorum to avoid split brain The number of voting members determines the cluster tolerance to failure

Configuring cluster quorum: 1. Select cluster members to vote

Primary

Auto failover target

Other nodes in local data center (not necessarily hosting SQL Server instances)

2. Select quorum type:

Odd number of votes, use “Node Majority”

Even number of votes

a) Add an additional node and use “Node Majority”

b) Add a file share and use “Node and File Share Majority”

EXAMPLE TOPOLOGY – CLUSTER QUORUM CONFIGURATION

ALWAYS ON ACTIVE SECONDARIES

ACTIVE SECONDARY – READABLE SECONDARY

OFFLOADING READ WORKLOADS

OFFLOADING READ WORKLOADS

OFFLOADING READ WORKLOADS

CONFIGURING SECONDARY AS READABLE

CLIENT CONNECTIVITY

Read / Write Workload Connecting using AG Listener

Connection using FAILOVER_PARTNER (if connection

string of existing applications can’t be changed)

Read Only Workload Connection using VNN and

ApplicationIntent=ReadOnly

Connection to the secondary instance directly

ReadOnly Routing

Multi subnet failover scenario: New client libraries => MultiSubnetFailover=True

Old client libraries configure appropriate client

connection timeout

CONFIGURING ROUTING OF READ-ONLY CONNECTIONS

CONFIGURING ROUTING OF READ-ONLY CONNECTIONS

READABLE SECONDARY – DATA LATENCY

LOG SYNCHRONIZATION TO SECONDARY

BACKUP* CAPABILITIES

*Database backup is copy-only type, Log backup is regular. See http://msdn.microsoft.com/en-us/library/hh245119.aspx

CREATING BACKUPS

SQL SERVER FAILOVER CLUSTERING COMPONENTS

ALWAYSON MULTI-SITE FAILOVER CLUSTER INSTANCE HA & DR SOLUTION

Provide High Availability at the Instance Level Unit of failover = SQL server instance

Maintain same virtual network name after failover. Clients re-connect to same name

Instance restart requires database to go through recovery

Provide Disaster Recovery at the Instance Level Provide Disaster Recovery protection from site failure: be it network, power, infrastructure or other site

disasters.

Require storage based replication technology and networking considerations

Multi-subnet support

ALWAYSON FAILOVER CLUSTER INSTANCES

MULTI-SUBNET CLUSTERING

ALWAYSON FAILOVER CLUSTER INSTANCE Failover Condition Policy

CONFIGURE NEW IP ADDRESS - ADDNODE

MULTI-SUBNET CLUSTERING REQUIREMENTS

SQL Server SKU: Enterprise Edition

OS version: Windows Server 2008 R2 +

SAN replication for cross-site DR (e.g. EMC SRDF)

Single AD domain for all nodes

Even number of nodes

BEST PRACTICES – 1. QUORUM MODE

BEST PRACTICES – 2. HEARTBEAT SETTINGS

Default Value Frequency is once per 1 second

If miss 5 heartbeat then initial failover

Tune the setting for cross subnet heartbeat CrossSubnetDelay can be up to 4 seconds

CrossSubnetThreshold can be up to 10

http://technet.microsoft.com/en-us/library/dd197562(WS.10).aspx

BEST PRACTICES – 3. SAN REPLICATION

Use block replication File and Application replication is not supported

Preserve block size and write-order to prevent data corruption

Choose Replication Mode according to the network latency Sync if Network latency < 10ms (regional DR)

Async if Network latency > 10ms (Geo DR)

http://technet.microsoft.com/en-us/library/dd197562(WS.10).aspx

BEST PRACTICES – 4. DNS SETTINGS

Parallel Client Connection (new client connection string parameters) sqlcmd.exe -M switch

ADO .Net, native clients MultiSubnetFailover=true

OLE DB, legacy clients Connection Timeout = 21* (# of IPs)

Reduce DNS replication delay DNS/AD inter-site replication schedule, by default is 180 minutes

Set replication frequency to 15 minutes (minimum value)

TEMPDB ON LOCAL DISK

Why We Enable This? Tempdb access occupies large % of SAN I/O

Fast local HDD/SSD becomes standard Server

configuration

Benefits Better overall performance

Cost saving

Important Note! Ensure that tempdb local paths are available to

SQL Service on all the nodes

PREDICTABLE RECOVERY TIME – INDIRECT CHECKPOINTS

Previously checkpoints mode (automatic vs. fixed intervals) Variance in failover time

Variance in IO load

New in SQL Server 2012: Background checkpointing over time

Smoother IO load

More predicable failover times

Configurable per database

Off-by-default for backcompat

INDIRECT CHECKPOINT: DIRTY PAGES

FLEXIBLE FAILOVER POLICY – Failure Condition Levels

WHY WINDOWS SERVER CORE FOR SQL SERVER 2012?

WINDOWS SERVER 2012 INSTALLATION

WINDOWS TIPS FOR SQL SERVER DEPLOYMENTS

http://tinyurl.com/cn7ttsm

http://tinyurl.com/28h883x

http://tinyurl.com/729mr58

.NET FRAMEWORK & SERVER CORE

http://tinyurl.com/d2uapdp)

o How To: http://tinyurl.com/6nmueob (DISM) or http://tinyurl.com/882un6y (PS)

.NET 3.51 (incl.

2.0)

How to Install .NET 4.0 How to Install

Windows Server

2008 R2

In Band Server Manager

(GUI), DISM,

PowerShell

Out of Band SQL media,

download

Install 4.0.2 or later

for AlwaysOn

enhancements

Windows Server

2012

In Band Server Manager

(GUI), DISM,

PowerShell

In Band Already enabled

(.NET 4.5)

.NET FRAMEWORK & SERVER CORE

DISM (Full) DISM (Core) PS (Full) PS (Core)

Windows Server

2008 R2

NetFx3 • NetFx2-ServerCore

• NetFx2-ServerCore-

WOW64

• NetFx3-ServerCore

• NetFx3-ServerCore-

WOW64

Net-Framework-

Core

Use DISM (will be

enabled with

remote

management)

Windows Server

2012

Net-

Framework-

Core

Net-Framework-Core

Net-Framework-

Core

Net-Framework-

Core

SQL SERVER 2012 INSTALL BEHAVIOR ON FULL GUI OS

• Have to manually install .NET Framework 3.51

• Will install .NET 4.0 (if necessary)

SQL SERVER 2012 INSTALL BEHAVIOR ON SERVER CORE

• Will enable/install .NET Framework (3.51 and 4.0) if not already done

WSFC & SERVER CORE

WSFC & SERVER CORE

DISM (Full) DISM (Core) PS (Full) PS (Core)

Windows Server

2008 R2

FailoverCluster-

FullServer

• FailoverClust

er-Core

• FailoverClust

er-Core-

WOW64

Failover-

Clustering

• Failover-

Clustering

• WoW64-

FailoverClust

er

Windows Server

2012

FailoverCluster-

FullServer

FailoverCluster-

FullServer

Failover-

Clustering

Failover-

Clustering

WSFC & SERVER CORE

DISM PS

PowerShell cmdlets • FailoverCluster-

AdminPak

• FailoverCluster-

PowerShell

RSAT-Clustering-

PowerShell

Old Automation

Server

(deprecated)

FailoverCluster-

AutomationServer

RSAT-Clustering-

AutomationServer

Old cluster.exe

(deprecated)

FailoverCluster-

CmdInterface

RSAT-Clustering-

CmdInterface

ACTIVATION WITHOUT INTERNET CONNECTIVITY

INSTALLING SQL SERVER 2012 ON SERVER CORE

o http://tinyurl.com/bmozrgw, http://tinyurl.com/cnft2fm

INSTALLING SQL SERVER 2012 ON SERVER CORE

http://tinyurl.com/7jovob2

INSTALLING SQL SERVER 2012 ON SERVER CORE

ADDITIONAL INFORMATION

The Microsoft SQL Server support policy for

Microsoft Clustering

http://support.microsoft.com/kb/327518

• KB943984 – The Microsoft Support Policy for Windows

Server 2008 or Windows Server 2008 R2 Failover Clusters

http://support.microsoft.com/kb/943984

• KB2545685 – Recommended hotfixes and updates for

Windows Server 2008 R2 SP1 Failover Clusters

http://tinyurl.com/7r8flpj

• SQL Server 2012 Bare Metal Workshop Series

http://tinyurl.com/7l66mks

• Server Core team blog http://tinyurl.com/7e4rq8o

NEXT STEPS

SQL Server 2012 Case Studies: http://www.microsoft.com/casestudies/Case_Study_Advanced_Search.aspx (Search on

SQL Technologies)

SQL Server 2012 Hands On Labs: http://www.microsoft.com/sqlserver/en/us/learning-center/virtual-labs.aspx

SQL Server 2012 Certification: http://www.microsoft.com/learning/en/us/certification/cert-sql-server.aspx

SQL Server 2012 Best Practices: http://technet.microsoft.com/en-us/sqlserver/bb671430

BETTER AVAILABILITY WINDOWS SERVER 2012

Enhanced Live Migration

Cluster-Aware Updating (CAU)

Windows Server Core

Dynamic Quorum in Cluster

Hyper-V Replica

Significantly decrease downtime

BETTER AVAILABILITY WITH WINDOWS SERVER TECHNICAL BENEFITS

KEY LEARNINGS FROM EARLY CUSTOMER DEPLOYMENTS

MULTI-SITE FAILOVER CLUSTER INSTANCE FOR HA AND DR

MULTI-SITE FAILOVER CLUSTER INSTANCE FOR HA AND DR Fileshare Witness in 3rd Data Center

MULTI-SITE FAILOVER CLUSTER INSTANCE Key Elements

A single SQL Server failover cluster instance (FCI) providing HA as well as DR Spanning across multiple sites (usually multiple subnets as well)

Key components: Storage

Storage level replication

Storage failover mechanism

Provided by the storage vendor

Work with your storage vendor to get the appropriate software and best practices

Network Multi-subnet support in SQL Server configuration and engine

Key improvement in SQL Server 2012

IP address OR dependency set within SQL Server setup

SQL Engine skips binding to any IP’s which are not online at start-up

RegisterAllProvidersIP for Network Name improves application failover time

MULTI-SITE FAILOVER CLUSTER INSTANCE Deployment Considerations

Storage Validation Storage Validation Check Requirement is relaxed due to make-up of multi-site storage

infrastructure (but still get the pop-up!)

Multi-site FCI Solution does not require passing the storage validation tests, to be

supported. http://support.microsoft.com/kb/943984

Appropriate Quorum Model Validation suggests “Node and Disk Majority” which can be ignored

Consider “Node and File Share Majority” or “Node Majority” based on number of nodes

MULTI-SITE FAILOVER CLUSTER INSTANCE Deployment Considerations

TEMPDB on Local Disk Not specific to “multi-site” FCIs, but has some great positive side effects for “multi-site”

scenarios

Enables use of local storage for TEMPDB

Can use solid state storage to improve performance of TEMPDB-heavy workloads

Saves money on storage replication cost

Reduces cross-data center storage replication traffic

AVAILABILITY GROUPS FOR HA AND DR

AVAILABILITY GROUPS FOR HA AND DR Deployment Considerations

Pre-requisites: BOL Link: Prerequisites, Restrictions, and Recommendations for AlwaysOn Availability Groups

(SQL Server)

Unit of Failover Group of databases – not the instance

Consider Contained Database for containing logins for failover

For jobs and other objects outside the database, simple customization needed

Considerations for Replacing Log Shipping No delayed apply on the secondary

Removing log shipping means the regular log backup job is removed

Need to re-establish periodic log backup (essential for truncating the log)

CUSTOMER EXAMPLE: MSIT SAP ERP

Business Critical to the Microsoft business

Utilized for finance, payment, and procurement among other functions, for Microsoft.

Utilized across 89 countries , supporting 92,000 employees

Application ~100K internal web users plus external web users

Up to 1500+ concurrent users

2 million dialog steps per business day

240K+ batch job executions per month

6.6 terabytes of compressed data

0.8 seconds user response time

99.995% availability

http://www.microsoft.com/casestudies/Microsoft-SQL-Server-2012-Enterprise/Microsoft-IT/Microsoft-Ensures-Smooth-Operation-of-ERP-

System-and-Cuts-Disaster-Recovery-Time/710000000493

CUSTOMER EXAMPLE: MSIT SAP ERP

SPECIAL CASE: AUTOMATIC FAILOVER FOR DR Use of 3rd Data Center

CUSTOMER EXAMPLE: BWIN.PARTY

Business Online gaming and gambling.

Real money handling system for bwin.party.

Authoritative system for Responsible Gaming Limitations.

Application Requirements Multiple databases, and multiple availability groups in the topology.

Plan for the worst case scenario: Loss of a complete datacenter.

Must still be able to do maintenance during the worst case.

RPO: Zero data loss.

RTO: 10 seconds or less.

>99.99% availability in the last number of years.

>99.99% availability even with maintenance.

http://www.microsoft.com/casestudies/Microsoft-SQL-Server-2012/bwin.party/Company-Cuts-Reporting-Time-by-up-to-99-Percent-to-3-

Seconds-and-Boosts-Scalability/710000000087

CUSTOMER EXAMPLE: BWIN.PARTY

FAILOVER CLUSTER INSTANCE (HA), AVAILABILITY GROUP (DR)

FAILOVER CLUSTER INSTANCE (HA), AVAILABILITY GROUP (DR) Deployment Considerations

Pre-requisites: Windows Server Service packs / QFEs:

Asymmetric Storage

Windows Server 2008 with http://support.microsoft.com/kb/976097

OR, Windows Server 2008 R2 SP1

Node Votes: http://support.microsoft.com/kb/2494036

Validate disk test QFE: http://support.microsoft.com/kb/2531907

Prerequisites, Restrictions, and Recommendations for AlwaysOn Availability Groups (SQL Server)

Different units of failover for HA and DR Instance-level failover for local HA (FCI)

Group of databases (AG) for DR

AG Failover Mode In FCI+AG configuration, FCI provides automatic failover, and AG provides manual failover

FAILOVER CLUSTER INSTANCE (HA), AVAILABILITY GROUP (DR) Deployment Considerations

Asymmetric Storage Key concept behind this architecture

New Windows Server Failover Clustering capability introduced in:

Windows Server 2008 R2 SP1

Windows Server 2008 with QFE

Symmetric storage = a cluster disk that is shared between all the WSFC nodes

Asymmetric storage = a cluster disk that is shared between a subset of nodes

Instance Naming Each FCI within the WSFC needs to have a different instance name

Database File Paths (recommended) use identical drive letters for the disks for each FCI

(recommended) use identical file paths for data and log files for each FCI

CUSTOMER EXAMPLE: SERVICEU CORP (PART OF ACTIVE NETWORK)

Business ServiceU provides web-based online scheduling, event management, payment processing, and other services to

customers in 15 countries and 50 united states.

Application Requirements 99.99% uptime (maximum allowable downtime of 52 minutes per year including scheduled maintenance).

Security – Level 1 PCI Service Provider.

Performance.

http://www.microsoft.com/casestudies/Microsoft-SQL-Server-2012/ServiceU/Online-Company-Reduces-Downtime-and-Helps-Its-Customers-

to-Improve-Service/4000011506

CUSTOMER EXAMPLE: SERVICEU CORP (PART OF ACTIVE NETWORK)

QUORUM CONSIDERATIONS

QUORUM MODEL AND NODE VOTES Availability Groups for HA and DR

QUORUM MODEL AND NODE VOTES Failover Cluster Instance (HA), Availability Group (DR)

QUORUM MODEL AND NODE VOTES How to set / view

MIGRATION PLANNING AND KEY CONSIDERATIONS

Hardware: new hardware, reuse existing hardware?

Windows Server: Upgrading the OS as well?

Windows Clustering: involve the Windows System Administration team and the networking

team Quorum considerations across multiple data centers

Cluster network communication across multiple data centers

Stages: migrate the whole configuration at once, or migrate the DR afterwards?

Application connection string change

If the secondary is a Failover Cluster Instance: needs re-seeding Uninstall existing SQL FCI on the DR site nodes

Destroy existing WSFC at the DR site

Join DR site nodes to Windows cluster created in the primary data center

Re-install SQL FCI on DR nodes

Backup database(s) from primary, and Restore on the secondary

SQL SERVER 2012 ALWAYSON CUSTOMER EXAMPLES

BETONSOFT

Business International gaming software provider.

Software development of online casino gaming platform.

Shared platform for 5 operators (15 brands).

Over 110 games, including: Slots, Roulette, Video Poker, Blackjack, Craps.

Application Game play data is generated rapidly and used infrequently for “Playback”.

Game state and game history.

Realtime operator metrics (less than 2 seconds).

http://www.microsoft.com/casestudies/Microsoft-SQL-Server-2012-Enterprise/BetOnSoft/Online-

Gaming-Firm-Implements-Real-Time-Analytics-and-Scales-for-Planned-Growth/710000000130

BETONSOFT - ARCHITECTURE

Infrastructure 1 data center. A separate DR data center is being planned.

Hardware Dell R810 servers with 4 X 8-core, 256 GB RAM.

Fusion IO cards for storage: Two cards on each server (1.2 TB, 640 GB).

AlwaysOn HA / DR Solution

BETONSOFT – HA ARCHITECTURE

SUMMARY: BETONSOFT

Gains and Learnings Modified application to remove distributed transactions

Distributed transactions were broken into two separate transactions and the application

handles consistency

AG synchronous replica has very minimal impact on performance and throughput of the

application

SOFTBANK (AGOOP) - WEBGIS

Business Softbank

One of the largest mobile phone carrier in Japan

Also runs broadband and international phone line

AGOOP

Subsidiary of Softbank

Specialized to GIS (Geographic Information Systems)

Provide services for Softbank and external customers

Application WebGIS is the GIS for internal Softbank mobile for analysis to help make plans for their future business

HA/DR requirements:

RPO=0

RTO=1 hour (unplanned), Up to 1/2 day for maintenance (planned)

http://www.microsoft.com/casestudies/Microsoft-SQL-Server-2012/SoftBank-Mobile-Corporation/Japanese-Cellular-Provider-Gains-High-

Availability-and-Improves-Performance/710000000498

SOFTBANK (AGOOP) - ARCHITECTURE

Infrastructure Single data center

Hardware Dell PowerEdge R710 servers, 2-Socket (16 logical cores total)

Storage: Powervault MD3000/MD1000

AlwaysOn HA / DR Solution

SOFTBANK (AGOOP) – HA ARCHITECTURE

SUMMARY: SOFTBANK (AGOOP)

Gains and Learnings AlwaysOn Availability groups provide a mechanism for High Availability and also for read-

scale.

Easy to scale out reads using AlwaysOn availability group and readable secondary

Previously had multiple data tiers with transactional replication, with AlwaysOn integrated solution.

With AlwaysOn maintenance overhead in managing different databases in the replication

architecture is gone.

Allowed analysts to create reports on data without impact to the primary workload.

DELL – TRANSIENTCART

Business Dell.com is one of the busiest websites in the world.

Over 10,000 concurrent users during peaks.

Most sales and support processes are executed online through Dell.com

Dell did $61 billion US in revenue for 2011.

Application TransientCart is a shopping cart for Dell.com

Maintains a user’s configuration for 45 minutes

Allows for users to quickly retrieve and store items without re-configuring every time.

Very heavy OLTP write application.

Multiple “carts” to handle load, consolidated into 1 for SQL Server 2012

Business requires 4 9’s uptime (including planned and unplanned downtime)

http://www.microsoft.com/casestudies/Microsoft-SQL-Server-2012-Enterprise/Dell/Dell-Speeds-Recovery-Time-by-99-Percent-Boosts-Service-

and-Efficiency-and-Cuts-Costs/710000000488

DELL - ARCHITECTURE

Infrastructure 2 data centers, distance of 1.5 miles apart

Different subnets in each data center

Hardware Dell PowerEdge R710 servers, 2-socket/8-core and 24Gb of RAM

Compellent SAN storage

AlwaysOn HA / DR Solution

DELL (TRANSIENTCART) - HA/DR ARCHITECTURE

SUMMARY: DELL TRANSIENTCART

Gains and Learnings Able to achieve failovers in less than 1 minute: RTO < 1 min.

Synchronous AG’s allow for RPO = 0.

Meeting SLA of 52 min downtime (99.99%), so far zero perceived downtime. Upgrade from RC to RTM had no application downtime impact

Listener (VNN) helped avoid extended manual process they previous had to go through in

a DR scenario.

Have a coordinated plan to recover from disaster. Worked with different groups to build

the system and maintain scripts and process to recover in case of failure.

In Process: Backup from secondary (waiting on support from 3rd party) and readable

secondary capabilities.

MICROSOFT IT SAP ERP DEPLOYMENT

Business Critical to the Microsoft business

Utilized for finance, payment, and procurement among other functions, for Microsoft.

Utilized across 89 countries , supporting 92,000 employees

Application ~100K internal web users plus external web users

Up to 1500+ concurrent users

2 million dialog steps per business day

240K+ batch job executions per month

6.6 terabytes of compressed data

0.8 seconds user response time

99.995% availability

http://www.microsoft.com/casestudies/Microsoft-SQL-Server-2012-Enterprise/Microsoft-IT/Microsoft-Ensures-Smooth-

Operation-of-ERP-System-and-Cuts-Disaster-Recovery-Time/710000000493

MSIT SAP ERP - ARCHITECTURE

Infrastructure 2 data centers ~160 miles apart

Hardware Database Servers: 4 X 8 cores, 256 GB of memory

EMC SAN

AlwaysOn HA / DR Solution

MSIT SAP ERP – HA/DR ARCHITECTURE

SUMMARY: MSIT SAP ERP

Gains and Learnings Replaced “combination of multiple technologies for HA + DR”, with a single technology

Required a lot of work across different IT teams

DO NOT MISS ! DB316 How does Microsoft run their SAP landscape on windows and SQL Server

Elke Bregler

Friday July 27, 13:00 - 14:15

MSIT – SERVICES INTEGRATION LAYER (SIL)

Business The Service Integration Layer (SIL) is a SOA based middleware messaging platform that

will expose common capabilities offered by the Microsoft Service & Support business.

This abstraction and services layer facilitates seamless integration of multiple service

consumers and service providers.

Application MSSOLVE, Metropolis, and other Incident Management systems would be leveraging SIL

for data access to downstream customers (EDW, DETEGO).

MSIT SIL - ARCHITECTURE

Infrastructure 2 data centers ~160 miles apart

Hardware 16 processors, 72 GB RAM

Direct attached storage

AlwaysOn HA / DR Solution

MSIT SIL – HA/DR ARCHITECTURE

SUMMARY: MSIT SIL

BWIN.PARTY

http://www.microsoft.com/casestudies/Microsoft-SQL-Server-2012/bwin.party/Company-Cuts-Reporting-Time-by-up-

to-99-Percent-to-3-Seconds-and-Boosts-Scalability/710000000087

BWIN.PARTY - ARCHITECTURE

Infrastructure Multiple data centers (3 used for the scenario we are focusing on here).

Data centers hosting primary and secondary replicas are 11 km apart

Hardware Fujitsu RX-600 S5 - 4 socket Nehalem-EX CPUs, 32 processor cores, 256 GB RAM

External SAS Disks for Data Files - Attached with 4x 8GB Fiber Channel, FusionIO SSD’s for Tlog

AlwaysOn HA / DR Solution

BWIN.PARTY – HA/DR ARCHITECTURE

SUMMARY: BWIN.PARTY

Eliminated need to maintain mirroring connection strings (failover_partner) in all

applications.

This was painful, and in some cases (some 3rd party applications) not even supported.

Eliminated Data Warehouse load restrictions due to Log Shipping (restore and query

conflict).

Migration involves other teams, not just the DBA team.

Troubleshooting now either needs way smarter DBAs or other teams involved.

Migration: Need to change connection string if more than 1 secondary replica.

Different machines used different OS versions before. This is no longer possible.

CAREGROUP HEALTHCARE

Four Hospitals located in Boston, MA

Among Top 5 Largest Healthcare Systems in the USA

146 Mission Critical Clinical Applications

2+ Million Patient Medical Records

Ranked #1: Most Innovative Healthcare IT nationwide (InformationWeek)

80+ databases rated “AAA”: RPO 0 & RTO 0

300+ databases rated “AA”: RPO =<1 hour & RTO 1 hour

Rest of the databases rated “A”: RPO & RTO 1 day

A “AA” class application is discussed in the next few slides.

http://www.microsoft.com/casestudies/Microsoft-SQL-Server-2012/Beth-Israel-Deaconess-Medical-Center/Hospital-

Improves-Availability-and-Speeds-Performance-to-Deliver-High-Quality-Care/5000000011

CAREGROUP – “AA” ARCHITECTURE

Infrastructure 2 data centers a few miles apart, collocated with the hospitals

Hardware Hardware for “AA” class of applications are virtualized using Hyper-V

EMC Clarion SAN used for storage

AlwaysOn HA / DR Solution

CAREGROUP “AA” – HA/DR ARCHITECTURE

SUMMARY: CAREGROUP HEALTHCARE

Test and validation

Performed parallel run for a week in pre-production

Performance of AG at par with DBM performance

Needed close working between Windows admin team and DBA team

Needed to rethink quorum model

MS DYNAMICS CRM ONLINE

Online with SQL Server 2012 ~4,000 customers.

2000+ Servers , 30000 + customers provisioned online, 200+ trials added each day

Multiple versions of CRM online supported at any given time

DB size ranging from 100 MB to 60+ GB, each organization gets their own database

Enable failovers at multiple levels and keep it simple

Redundancy and fault recovery at all levels

Business continuity and SLA commitments

99.99% (4 9’s availability)

MS DYNAMICS CRM ONLINE- ARCHITECTURE

Infrastructure 6 data centers worldwide, 2 in each geography (primary and DR)

Multiple subnets

Hardware HP ProLiant, 2 socket Intel Quad-Core Xeon L5630 2.26GHz, 48GB Memory, 1TB DASD

Two embedded Gb Ethernet NICs, P410 Smart Array controller with 256MB BBWC; N+1 Redundant

AlwaysOn HA / DR Solution

DYNAMICS CRM ONLINE – HA/DR ARCHITECTURE

SUMMARY: MS DYNAMICS CRM ONLINE

Performed successful Availability Group failovers in production.

Performed successful data center failover in production (Hongkong failing over to Singapore).

Simple and Unified:

New architecture that natively supports multiple data centers and meets all HA/DR needs with SQL Server 2012

Important Gaps Filled:

Parallel performance testing with Database Mirroring technologies

Successfully pushed AlwaysOn technologies past recommended boundaries

Identified multiple product development bugs and issues

Compliance with Microsoft Business Continuity Standards

Ready for ISO Certifications

Removed a big road block for enterprise adoption

Consistent, Solid Foundation:

Big step towards a future of further scale and robustness for CRM Online service

SUNDIO GROUP

Leading tour operator in Europe.

Sells trips to holiday destinations throughout Europe.

10 brands, 9 countries

Over 700K passengers in 2011

Online travel reservation system

http://www.microsoft.com/casestudies/Microsoft-SQL-Server-2012/Sundio-Group/Online-Travel-Firm-

Boosts-Availability-and-Performance-to-Handle-Peak-Sales-Volumes-with-Microsoft-

Solution/4000011822

SUNDIO GROUP - ARCHITECTURE

Infrastructure 1 data center

Hardware HP BL680 G7 blade servers

EMC VMAX SAN

AlwaysOn HA / DR Solution

SUNDIO GROUP – HA/DR ARCHITECTURE FCI for local HA, AG for Offloading read workload

SUMMARY: SUNDIO GROUP

Failover Cluster Instance and Availability Groups (FCI + AG) solution

FCI used for HA

AG used for offloading read workload

Use possible owners appropriately to ensure they don’t overlap for AG primary and AG

secondary

Transactional replication for read scale out

For the workload that requires only a subset of the data and different indexes

BALTIKA BREWERIES

The leader of the Russian beer market with 39.7% market share.

The largest FMCG (Fast Moving Consumer Goods) company in Russia.

The Baltika brand is the №1 beer in Europe in terms of sales (Euromonitor)

Annual Revenue: 79,307 million RBL or 2,643 million USD - (2010 year)

CRM Application through ISV-Monolit.

The core of Baltika’s selling process.

Provides a workspace for sales reps, merchandisers, service agents:

Taking and processing orders from distributors

Data for sales and marketing analytics

1500 back office/5000 mobile employees, 350 distributors.

100 000 orders a day, 50 000 distributor’s data exchange sessions a day.

Tier 1 application: 24x7 nonstop services as accessed from different regions and time-zones

http://www.microsoft.com/casestudies/Microsoft-SQL-Server-2012-Enterprise/Baltika-Brewing-Company/Brewer-Increases-

Efficiency-and-Insight-Boosts-Performance-by-up-to-78-Percent/710000000527

BALTIKA - ARCHITECTURE

Infrastructure 1 data center

Hardware HP ProLiant BL685c G7 Four 12-Core AMD Opteron, 2200 MHz proc., 256 Gb RAM

HP EVA

AlwaysOn HA / DR Solution

BALTIKA – HA/DR ARCHITECTURE

SUMMARY: BALTIKA

No impact/overhead on Primary replica when using Asynchronous secondary

Read-scale was able to be implemented via Availability Groups readable secondary replicas

Graphic below shows # of commands (1k-9M) and time (seconds) to deliver transactions 100k commands the time for replication goes up significantly

SERVICEU CORP (PART OF ACTIVE NETWORK)

ServiceU provides web-based online scheduling, event management, payment processing, and other services to

customers in 15 countries and 50 united states.

99.99% uptime (maximum allowable downtime of 52 minutes per year including scheduled maintenance).

Security – Level 1 PCI Service Provider.

Performance.

Try to eliminate manual intervention as much as possible.

Eliminate single points of failure as much as possible.

Highly trained personnel, extensive monitoring, good documentation, standardization across the enterprise.

http://www.microsoft.com/casestudies/Microsoft-SQL-Server-2012/ServiceU/Online-Company-Reduces-Downtime-and-

Helps-Its-Customers-to-Improve-Service/4000011506

Infrastructure 2 data centers ~500 miles apart. Each data center is identical in capacity and infrastructure

Hardware Dell R815 (2 X 12 cores), 128 GB RAM

EMC SAN

AlwaysOn HA / DR Solution

SERVICEU - ARCHITECTURE

SERVICEU - HA / DR ARCHITECTURE

SUMMARY: SERVICEU

Upgraded to SQL Server 2012 with 90 seconds of downtime (half of which was actual upgrade

downtime, and the other half for final testing during the upgrade).

Asymmetric disk as quorum resource.

DO NOT use Windows Failover Cluster Manager to perform Availability Group Failover.

Concurrent ADD NODE operation yields unexpected results in a SQL Server Failover Cluster Instance.

Ensure correct possible owners have been set for each resource within each FCI.

In a FCI + AG setup, the SQL Instance names must be unique within the Windows Cluster.

EDGENET

Leader in Data Services, Guided Selling and Marketing Solutions

Organize product information to increase sales: Help retailers sell configurable products

Help consumers compare and purchase the right product for them.

Collect, certify and distribute product data Google/Bing Search & Shopping, and for Retailers

One of Four Active US GDSN-certified pools

Provides high availability and disaster recovery for data within the pool of applications above Near real-time data replication with MSDTC support

Need for data to be available for Exports & BI Workloads

SLA: 99.99% Annual uptime

http://www.microsoft.com/casestudies/Microsoft-SQL-Server-2012/Edgenet/Data-Provider-Supports-Growth-and-

Gains-Competitive-Advantage-with-Microsoft/4000011528

Infrastructure 2 data centers: Milwaukee, WI and Atlanta, GA (850 miles in between)

Multiple subnets

Hardware NEC Express 5800/A1080a-D GX

EMC Clariion CX4-80, EMC Recover Point CE – Disk Based Replication

AlwaysOn HA / DR Solution

EDGENET - ARCHITECTURE

EDGENET - HA / DR ARCHITECTURE

SUMMARY: EDGENET

Allowed for true multi-site failover without having to create a VLAN.

Advantage of TempDB on Local Disk Saves money on storage replication cost.

Reduces cross-data center storage replication traffic.

Enables use of local solid state storage to improve performance.

Provided ability to offload BI workload and exports to read-only secondary database.

RESOURCES

© 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market

conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

© 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market

conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.