What’s New in Microsoft SQL Services

Nigel EllisArchitectMicrosoft SQL Services

Agenda

Year in review: SDS learning

Database Service Value Proposition

Relational Database-as-a-Service

Architecture and breadth

Roadmap

Place

Type

Service

Data Platform: Device to Cloud

Mobile/Desktop

AnalysisCaching

Integration

Sync

Search

Data ServicesServerDesktop

RelationalBLOB

QueryBackup

Load

MultiDim

Mega-server

InMemory FileXML

ReportingMiningProtection

RDBMS

Model & policy based development and management

Extending SQL Data Platform to Cloud

SQL Data Services (SDS)Database-as-a-Service

Data SyncReference Data

Reporting

Business Intelligenc

e

Symmetric Programming Model

Initial services – core RDBMS capabilities as a service (SDS), Data Sync and Data HubFuture Offerings

Additional data platform capabilities as a service: BI/DSS, DWNew services: Reference Data, Secure Data Hub

Data Hub Aggregation

Enable new uses of data to deliver differentiated business value

The New SQL Data Services

Familiar SQL Server relational modelUses existing APIs & toolsBuilt for the Cloud with availability and scaleAccessible to all from PHP, Ruby, and Java

Clear Feedback: “I want a database in the Cloud”

Focus on combining the best features of SQL Server running at scale with low friction

The Evolution of SDS

Evolv

es

SDS Next

TDS + TSQL Model

Web App

SQL Client*

Windows Azure

BrowserApplicatio

n

Application

REST Client

REST (Astoria)

ADO.Net + EF

Application

SQL Client*

Cloud

HT

TP

HT

TP

+R

ES

T

TD

S

* Client access enabled using TDS for ODBC, ADO.Net, OLEDB, PHP-SQL, Ruby, …

Data

Cen

ter

ODBC, OLEDB, ADO.Net PHP, Ruby, …

SDS Current

REST/SOAP + ACE Model

Web App

REST Client

Windows Azure

BrowserApplicatio

n

Application

REST Client

HT

TP

HT

TP

+R

ES

T

Data

Cen

ter

Cloud

Database ChoicesR

eso

urc

es

Dedicated

Shared

Low High“Friction”/Control

Low-cost and zero friction addresses web/dept workloadsHigh compatibility with existing SQL Server offering

SDS (RDBMS)

Value Props:

Auto HA, Fault-ToleranceFriction-free scaleSelf-provisioningHigh compatibility

Virtual DB server Logical user database

(LDB) Resource governance @

LDB Security @ LDB

Value Props:

XSPs, Server OpsSQL CLR100% compatibility

Roll-your-own HA/DR/scale

Hosted Hosted SQL Server or

other Resource governance @

VM Security @ DB Server/OS

On-premise SQL Server or other s/w on-

premise Resource governance @ machine Security @ DB Server/OS

Value Props:Full h/w control –

size/scale100% compatibilityRoll-your-own

HA/DR/scale

Demo: Accessing SDS from PHP

PHP runs in Azure using FastCGI

Access to SDS via existing drivers

Ease of provisioning

SQL Data Services

TDS + TSQL Model

Wordpress (PHP)

BrowserApplication

Internet

HTTP

Mic

roso

ft D

ata

C

en

ter

Windows Azure

ODBC

TDS+SSL

Service Provisioning ModelEach account has

a billing relationship with Microsoftowns one or more virtual servers

Each server has one or more databases including virtual mastereach database limited in size one or more logins

Each database has one or more SQL users

Account

Server

DatabaseServer=server1.data.database.windows

.netDatabase=testDBLogin=nigele[@server1] (maps to

testuser)

Logical Databases (LDB)

Shared infrastructure at SQL database and below

Request routing, security and isolation

Scalable HA technology provides the glueAutomatic replication and failover

Provisioning, metering and billing infrastructure

Machine 5

SQL Instance

SQL DB

DB5 DB1 DB3 DB2

Provisioning (databases, accounts, roles…), Metering, and Billing

Machine 6

SQL Instance

SQL DB

DB1 DB6 DB2 DB3

Machine 4

SQL Instance

SQL DB

DB3 DB4

Machine 7

SQL Instance

SQL DB

DB4 DB5 DB1

Scalability and Availability: Fabric, Failover, Replication, and Load Balancing

SQL Tooling and Development

demo

Compatibility Goals

Support common application patternsLogical/policy based administrationPatterns work from Server to CloudMulti-tenancy considerations

Throttling and load balancingLimits on DB size, transaction duration, …

V1: Address the needs of 95% or more web and departmental application

Example of SQL CompatibilityIn Scope for v1 (likely)

Tables, indexes and viewsStored ProceduresTriggersConstraintsTable variables, session temp tables (#t)…

Out of Scope for v1 (likely)

Distributed TransactionsDistributed QueryCLRService BrokerSpatialPhysical server or catalog DDL and views

Connection Model

Clients connect directly to a databaseMost SQL supported within databaseCannot hop across DBs

DB’s can be on different servers so state management is hard

Connection tied to target database; cannot “hop” across

Security Model

Uses regular SQL security modelAuthenticate logins, map to users and rolesAuthorize users and roles to SQL objects

Limited to standard SQL Auth loginsUsername + password

Future AD Federation, WLID, etc as alternate authentication protocols

Security model is 100% compatible with on-premise SQL

Platform Readiness (EHA)

Exchange Hosted Archive (EHA) is high scale archival serviceRuns on SDS infrastructure

In production prior to SDS v1Rebuilt to address cost and scale issueshttp://go.microsoft.com/fwlink/?LinkId=145374

Reduced COGS with increased customer and business benefit: Larger scale (e.g. larger customers ~20TB+

each) More self-managing (e.g. fault-tolerance)

Better query performance for fan-out Faster provisioning of new customers

SQL ServicesOpportunities and Futures

Partitioned databasesGeo-location and geo-redundancyDistributed querySecurity w/AD, WLID, etcSupport for multiple levels of hardware and software isolation

Release Plan

Invitation CTP – On-board invitation-only customers + some current

Public CTP – On-board all early adopters

Commercial Availability with Windows Azure in 2009

MIX ‘09

TechEd WWPC

InvitationCTP

Public CTP

Commercial Availability

Migration

Mar 09

May 09 Jul 09 Nov 09

Sep 09

Apr 09

Jun 09 Aug 09

Oct 09

PDC

InternalAdoption

Key Takeaways

Foundation of the SDS relational platform

Built using core SQL Server product codebase

Delivery of rich relational database service – PDC ’09

Key capability of the Azure platform

Supports broad spectrum of scenarios

Please Complete an Evaluation FormYour feedback is important!

Evaluation forms can be found on each chairTemp Staff at the back of the room have additional evaluation form copies

Want to Know More?

Team Bloghttp://blogs.msdn.com/ssds

MSDN Development Centerhttp://msdn.microsoft.com/en-us/sqlserver/dataservices

© 2009 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.

SQL Data Services

Clear Feedback: “I want a database in the Cloud”

Familiar relational modelT-SQL, Tables, DML, DDL, Indexes, SPs...

Leverage existing toolsExtends on-premises apps

Zero-friction provisioningScale-free & easy to manageAutomatic HA, fault-tolerance and geo-location support

Highly interoperableBreadth developer support

PHP, Ruby, JavaOSS libraries and frameworks

SDS delivers…

SQL Data Services combines the best features of

simple storage and hosted RDBMS

Replaces current “Flex Entity” Data Model and Protocol Support

ADO.NET Data Services – REST/HTTP support

Windows Azure Storage – “property bag” data model

Logical vs. Physical Administration

SDS focus on logical administrationMove to policy based management

Data management, config and availability

Automatically replicated with HA “out of box”Transparent failover in case of failureLoad balancing of data to ensure SLA

DBA role places more focus on policy/logical management

TDS Gateway

Front-end NodeProtocol Parser

Gateway Logic

TDSSession 1

Front-end NodeProtocol Parser

Gateway LogicTDS

Session 2

High Level Architecture

Master Cluster

Master Node

Data Node Components

Partition Manager

Master Node

Data Node Components

Partition Manager

1

2

4

5

6

7

8

Utility Layer

Account Database

Billing/Usage

Database

Service Platform

Monitoring

Load Balancing

NodeProvisionin

g

Roles

3

Machine 5

SQL Instance

SQL DB

DB5 DB1 DB3 DB2

Scalability and Availability: Fabric, Failover, Replication, and Load balancing

Machine 6

SQL Instance

SQL DB

DB1 DB6 DB2 DB3

Machine 4

SQL Instance

SQL DB

DB3 DB4

Machine 7

SQL Instance

SQL DB

DB4 DB5 DB1

Scalability and Availability: Fabric, Failover, Replication, and Load balancing