sql azure database: present and future

35
SQL Azure Database: Present and Future Tony Petrossian Principal Program Manager SVC52 Dave Campbell Technical Fellow

Upload: mohammad-freeman

Post on 01-Jan-2016

39 views

Category:

Documents


0 download

DESCRIPTION

SVC52. SQL Azure Database: Present and Future. Dave Campbell Technical Fellow. Tony Petrossian Principal Program Manager. Agenda. SQL Azure Overview Service Roadmap SQL Azure Database Future SQL Azure Future. The Power of the SQL Data Platform in the cloud - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: SQL Azure Database: Present and Future

SQL Azure Database: Present and Future

Tony PetrossianPrincipal Program Manager

SVC52

Dave Campbell Technical Fellow

Page 2: SQL Azure Database: Present and Future

Agenda

> SQL Azure Overview > Service Roadmap> SQL Azure Database Future> SQL Azure Future

Page 3: SQL Azure Database: Present and Future

Database

Business AnalyticsReporting Data Sync

The Power of the SQL Data Platform in the cloud

Leverages existing skills and rich tooling ecosystem

Enables database applications with new, “cloud”

capabilities

SQL Data Platform as a Service – beyond hosting

Page 4: SQL Azure Database: Present and Future

SQL Azure Database

Customer Value Props

Self-provisioning and capacity on demand

Symmetry w/ on-premises database platform

Automatic high-availability and fault-tolerance

Automated DB maintenance (infrastructure)

Simple, flexible pricing – “pay as you grow”

MSDatacente

r

Windows Azure

Compute

Browser

SOAP/RESTHTTP/S

T-SQL (TDS)

App Code(ASP.NET)

SQL Server Report Server

(on-premises)

ADO.NET/REST - EDMHTTP/S

- AD Federation (LiveId /AppFabric AC)

SQL AzureDatabase

T-SQL (TDS)

Relational database service

• SQL Server technology foundation

• Highly symmetrical

• Highly scaled

• Highly secure

Database “as a Service” – beyond hosting

Highly scaled out relational database as a service

Database

Page 5: SQL Azure Database: Present and Future

SQL Azure Service Provisioning

> Each account has zero or more servers> Azure wide, provisioned in a common portal

> Billing instrument

> Each server has one or more databases> Contains metadata about the databases

> Unit of authentication and security

> Unit of Geo-location

> The server is a logical grouping of your DBs

> Each database has standard SQL objects> Unit of consistency

> Contains users, tables, views, indices, etc…

Account

Server

Database

Page 6: SQL Azure Database: Present and Future

SQL Azure Database

demo A view from tools & Portal

Page 7: SQL Azure Database: Present and Future

• South Central USA• North Central USA (Dec-2009)• Southeast Asia• North Europe

Additional sub-regions will be deployed in lock-

step with Windows Azure Platform

Timeline

Global Availabilit

y

Service Update

Service Update

Service Update

Rhythm

PDC 2009Ready for Go-Live

1/1/2010Start Billing

2/1/2010End Free Period

Service Update

Service Update

Service Update

Service Update

First half of the year

Second half of the year

Page 8: SQL Azure Database: Present and Future

SQL Azure Database

Future

Page 9: SQL Azure Database: Present and Future

>>FUTURE

Our goal is to provide the best end-to-end experience forenterprise departmental apps and SaaS ISV scenarios

Improve Tools• For Developers & Designers to build apps• For Administrators to manage the database lifecycle

SQL Azure Database: Future

Page 10: SQL Azure Database: Present and Future

Tools, Clients, Languages

> Today With the existing SQL Server ecosystem we have a fantastic start for our V1 offering> VS, SSMS, ADO.NET, ADO.NET Data

Services, PHP, Java…

> But we are also making huge investments for the future

Page 11: SQL Azure Database: Present and Future

>>FUTURE

Our goal is to provide the best end-to-end experience forenterprise departmental apps and SaaS ISV scenarios

Improve Tools• For Developers & Designers to build apps• For Administrators to manage the database lifecycle

SQL Azure Database: Future

Improve the operational model for enterprise users and SaaS providers• Backups, integration with on-prem…

Page 12: SQL Azure Database: Present and Future

>>FUTURE

Database BackupsFailure Scenario Solution When Responsible

Party

HW and Media failures

Multiple replicas of all databases with automatic failover. System backups for additional protection

Today SQL Azure - Built-in to the base serviceX

Customer application or administrator errors leading to data loss

Use BCP, SSIS or other custom tools to backup data Today Customer

Database clone to create on-demand, backups of databases in the local or remote SQL Azure region

• Cloning is done with transactional consistency

• When clone operation is complete the replica is accessible as a normal database

1H 2010

Customer

Page 13: SQL Azure Database: Present and Future

>>FUTURE

South Central US

abc.database.windows.net

Dev1Maste

r

xyz.database.windows.net

prod1Maste

r

CREATE DATABASE xyz.prod2clone AS CLONE OF xyz.prod2 CREATE DATABASE efg.prod2clone AS CLONE OF xyz.prod2

prod2cloneprod2clone

prod2cloneprod2clone

North Central US

efg.database.windows.net

DR1Maste

rprod2cloneprod2clone

CREATE DATABASE abc.prod2clone AS CLONE OF xyz.prod2

Database Clone

Prod2

Page 14: SQL Azure Database: Present and Future

>>FUTURE

Database BackupsFailure Scenario Solution When Responsible

Party

HW and Media failures

Multiple replicas of all databases with automatic failover. System backups for additional protection

Today SQL Azure - Built-in to the base serviceX

Customer application or administrator errors leading to data loss

Use BCP, SSIS or other custom tools to backup data Today Customer

Database clone to create on-demand, backups of databases in the local or remote SQL Azure region

• Cloning is done with transactional consistency

• When clone operation is complete the replica is accessible as a normal database

1H 2010

Customer

Continuous Backup option with point-in-time restore capabilities

• Configurable retention and lag period• Backups available for read operations• Local or remote region

2H 2010

1. Customer enables and configures it.

2. Service will maintain it

Page 15: SQL Azure Database: Present and Future

>>FUTURE

Operational Models> Support for SaaS providers

> Provisioning APIs for ISVs> Template database support> Meta-data tracking> Additional billing scenarios

SaaS:SQL Azure is a highly available and scalable database service and an excellent option for building and managing multi-tenant services.

> Single unit for deployment and upgrades (DAC)

> Data Synchronization

Enterprise:integration with on-premises environments

> Upgrade and downgrade options between SKUs

> Read only databases

Page 16: SQL Azure Database: Present and Future

>>FUTURE

Our goal is to provide the best end-to-end experience forenterprise departmental apps and SaaS ISV scenarios

Improve Tools• For Developers & Designers to build apps• For Administrators to manage the database lifecycle

SQL Azure Database: Future

Improve the operational model for enterprise users and SaaS providers• Backups, integration with on-prem…

Improve the application programming model• Simplify the building of highly scalable applications• Further improve symmetry with on-premises SQL Server

Page 17: SQL Azure Database: Present and Future

Scale-out Support - TodayDatabase and workload partitioning is a classic technique for harnessing the power of many computers to achieve:

• Better price/performance • Levels of throughput not possible with a single machine

Classic scale-out challenges addressed by SQL Azure:

Highly available service on top of commodity hardware Zero administration cost of cluster HW, OS and SW No downtime Access to elastic pool of resources Pay as you grow No-friction provisioning of databases Create databases without ever running out of HW

Page 18: SQL Azure Database: Present and Future

SQL Azure

Castellan

Castellan Venue

DB

Castellan Venue DB’s

Venue 1Partition(

s)

Castellan Venue

DB

Castellan Venue DB’s

Venue 2 Partition(

s)

Castellan Venue

DB

Castellan Venue DB’s

Venue N Partition(

s)

One application DB, many venue DB’s – each partitioned in to many parts (40+)

...

Azure Roles

http:// TicketDirect .* Dynamic Worker(tasks

uploaded as blobs)

Partitioner Worker

Azure StorageQueues for communication between clients and roles

-- - --- - -

-- - --- - -

Tables to record server & partition information

Blobs to store web and worker role resources

Client Applications

Castellan.old (VB6)

Castellan.Azure• Box Office sales• Ticket Printing • System Administration • Venue/Event Management• Partitioning

.Net Service Bus

WCF

On PremiseSQL Server

Castellan Venue

Distributed Cache Worker

MemCache

TicketDirect Architecture

Page 19: SQL Azure Database: Present and Future

>>FUTURE

More Scale-out Support

o Dynamic database splits

o Ability to merge databases

o Improved schema management across group of databases

o Additional database size options

G1 G2

G4

G7

G5

G8

G3

G6

G9 G10

Page 20: SQL Azure Database: Present and Future

SQL Azure Database

Fan-out Demo

Page 21: SQL Azure Database: Present and Future

>>FUTURE

Recent Customer Feedback/Requests> Add support for profiler, DMVs …> Support for Spatial data types> Full-text search support> Change Tracking support> Support for CLR> Cloud based Business Intelligence (BI)

solutions> Encryption support> Additional Authentication models for login

(WIF)Come give us your feedback at the SQL Azure Lounge

Page 22: SQL Azure Database: Present and Future

Take Away

> Database as a service

> Lower TCO

> Automatic High Availability

> Automatic maintenance

> Instantly scale up or down databases as needed

> Metered by database

> Secure database with familiar AuthN/AuthZ model

> Mission-critical SQL Server foundation

Page 23: SQL Azure Database: Present and Future

Trustworthy Data Collaboration SQL Azure Codename ‘Vidalia’Dave CampbellTechnical FellowMicrosoft Corporation

Page 24: SQL Azure Database: Present and Future

>>FUTURE

Cloud is great place to connect

Empowers multiple parties

Businesses need control

Enable trustworthy collaboration for highly sensitive business data across disparate

trust domains

Sharing to trustworthy collaboration

Page 25: SQL Azure Database: Present and Future

Control of sensitive business data

• Control of infrastructure

• Control of policy & enforcement

• Control of data

Current Enterprise

Data

Infrastructure

Policy

Enforcement

Page 26: SQL Azure Database: Present and Future

>>FUTURE

• Control of policy & enforcement

• Limited infrastructure control

• Trustworthy collaboration with sensitive business data

SQL Azure

Policy

EnforcementPolicyEnforcement

Policy

Enforcement

Control of Sensitive Business Data

Data

Infrastructure

Policy

Enforcement

Page 27: SQL Azure Database: Present and Future

>>FUTURE

SQL Azure Codename ‘Vidalia’

Collaboration needs Approach

• PrivacyData and query

• ControlPolicy and enforcement

• AccountabilityData integrity and auditability

• Data-centric securityPolicy-based data encryption

• Federating accessSeparating data control from store

• Audit as a serviceAudit logs with controlled accessTamper detection

Page 28: SQL Azure Database: Present and Future

>>FUTURE

• Separates data control from store

• Issues capabilities to encrypt/decrypt data

• Empowers customers and partners

Collaboration with sensitive data

Privacy

ControlAccountabilit

y

Trustworthy Collaboration Example

Sensitive Business

Data

PublishersData Owners

Sensit

ive

busines

s dat

a Sensitive

business data

Subscribers

Auditors

Audit logs

SystemAdministrators

Capability Generation

Center

Page 29: SQL Azure Database: Present and Future

Pharmaceutical Reagent Data Mart

Rahul AuradkarDirectorMicrosoft Corporation

demo

Page 30: SQL Azure Database: Present and Future

>>FUTURE

Trustworthy Collaboration Scenarios

eHealthBusiness and legal

compliance

Regulated data

transfers

Trusted audit log

SQL Azure Codename ‘Vidalia’

Pharma clinical trial

Page 31: SQL Azure Database: Present and Future

Take Away

> SQL Azure Codename ‘Vidalia’ emerging approach to trustworthy collaboration

> Privacy provided through data-centric security

> Separating access enforcement from data service puts data owner in control of data

> Audit as a service and tamper detection methods enable accountability

[email protected]

Page 32: SQL Azure Database: Present and Future

YOUR FEEDBACK IS IMPORTANT TO US!

Please fill out session evaluation

forms online atMicrosoftPDC.com

Page 33: SQL Azure Database: Present and Future

Learn More On Channel 9

> Expand your PDC experience through Channel 9

> Explore videos, hands-on labs, sample code and demos through the new Channel 9 training courses

channel9.msdn.com/learnBuilt by Developers for Developers….

Page 34: SQL Azure Database: Present and Future

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

Page 35: SQL Azure Database: Present and Future