SQL Azure the database in the cloud

The database in the cloud forAzure Services Platform, SQL Azure
Ing. Eduardo Castro, PhD
Comunidad Windows
ecastro@grupoasesor.net
http://ecastrom.blogspot.com

Session Objectives And Takeaways
Session Objectives:
Provide “why”, “what”, and “how” around SQL Azure
Help you to answer your customer’s Cloud questions
Key Takeaways
Microsoft will have a strong position in Cloud business software
SQL Azure is different than SQL Server and hosted SQL Server
SQL Azure will open up new scenarios and opportunities

Session Structure

What’s up with the Cloud?

What’s going on out there?
Cloud perception… Costs? New capabilities? Massively scalable computing?
IaaS, PaaS, SaaS ???
Value chains being remade
Private clouds?
Interop & standards…

A Working Definition of Cloud Computing
Cloud computing is a model for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction.
This cloud model promotes availability and is composed of five essential characteristics, three service models, and four deployment models.
NIST, Information Technology Laboratory
6

7
5 Essential Cloud Characteristics
On-demand self-service
Broad network access
Resource pooling
Location independence
Rapid elasticity
Measured service
NIST, Information Technology Laboratory

Business View
New
Capabilities
Reducing
Costs
Opportunities
Risks
Remaking value, decision & influence chains…

Microsoft, Cloud & “business software”…

Platform dimensions
Relationship
Productivity
Friction
Velocity
Facilities
Focus
Viability
Trust
Scale
Characteristics of Software Platforms
Platform vendors succeed when the platform helps others succeed

Cloud Success Factors
Utility Computing Capability
Technical capability
Datacenter Innovation capability
Application Pattern Capability
Not just about the browser
Multi-screen experience
Platform, delivery & tooling
Platform Ecosystem
Work with ISVs, SIs, VARs & Businesses to get to Cloud

Challenges
Identity and Access Management
Composition / Workflow
2PL  OCC  Sync  Workflow
Trust
Availability
Performance
Information protection
Latency
It matters
Separating logical / physical administration

Microsoft Value Proposition
Provide
“Multi-screen”Experience
Provider
Of Choice
Provider
w/ Choice
Customers
Hosters
ISVs
SIs
VARs
Existing
BusinessProcesses
Partners
Billing as a Service
ServiceComposition
Internal
Processes &
Capabilities
SaaS influencing OPS & Services
PaaSBuildout
Extreme Scale Data Centers
MSR
PartnerEcosystem
Learning &
Growth
SaaS
Experience
(BPOS)
IaaS
Experience
(Live)
On-premises
Software (OPS) to
Services
Learning w/
Partners

What is “SQL Azure”?

The Azure Services PlaformAn illustration
.NET Services
SQL Azure
Applications
Windows Azure
Applications
Windows
Mobile
Windows
Vista/XP
Windows
Server
Others

Microsoft Azure Services
Azure™ Services Platform
16

SQL AzureA relational DB in the cloud
SQL Azure Database
Data Hub
Others (Future)
Relational database as a service
Highly available, automatically maintained
Extension of the SQL Server Data Platform
.NET Services
SQL Services
Applications
Live Services
Windows Azure
Applications
Windows
Mobile
Windows
Vista/XP
Windows
Server
Others

Extending SQL Server Data Platform to the Cloud
Data Sync
Reference Data
Reporting
Business Intelligence
Database
Symmetric Programming Model
Data Hub Aggregation
Initial services – core RDBMS capabilities with SQL Azure Database, Data Sync
Future Offerings
Additional data platform capabilities: Reporting, BI
New services: Reference Data

The New SQL Data Services
Clear Feedback: “I want a database in the Cloud”
Familiar SQL Server relational model
Uses existing APIs & tools
Built for the Cloud with availability and scale
Accessible to all from PHP, Ruby, and Java
Focus on combining the best features of SQL Server running at scale with low friction

The Evolution of SDS
Evolves
BrowserApplication
Application
Application
BrowserApplication
Application
ODBC, OLEDB, ADO.Net PHP, Ruby, …
REST Client
SQL Client*
REST Client
Cloud
Cloud
Windows Azure
REST (Astoria)
Web App
ADO.Net + EF
REST Client
HTTP+REST
HTTP+REST
HTTP
TDS
HTTP
Windows Azure
Web App
SQL Client*
Data Center
Data Center
TDS + TSQL Model
REST/SOAP + ACE Model
SDS Next
SDS Current
* Client access enabled using TDS for ODBC, ADO.Net, OLEDB, PHP-SQL, Ruby, …

Database
Relational database, provided as a service
Highly symmetrical development and tooling experience (use TDS protocol and T-SQL)
Highly scaled out, on commodity hardware
Built on the SQL Server technology foundation
Beyond “hosted database”
High availability, DB provisioning, and DB management are provided by the service
Pay for what you use

Customer Scenarios
Enterprise Departmental Applications
Web Applications
Departmental workgroup applications with low concurrency and cyclical usage patterns
Small customers or start ups with Web applications of all scale that have simple RDBMS needs
Data Hubs
ISV LOB Applications
Data hubs that consolidate multiple data sources and enable access from multiple locations and devices
Traditional ISVs extending offering or selling software hosted in the cloud

Service Provisioning Model
Each account has
a billing relationship with Microsoft
owns one or more virtual servers
Each server has
one or more databases including virtual master
each database limited in size
one or more logins
Each database has
one or more SQL users
Account
Server
Database
Server=server1.data.database.windows.net
Database=testDB
Login=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 glue
Automatic replication and failover
Provisioning, metering and billing infrastructure
Machine 5
Machine 6
Machine 4
Machine 7
SQL Instance
SQL Instance
SQL Instance
SQL Instance
SQL DB
SQL DB
SQL DB
SQL DB
Provisioning (databases, accounts, roles…), Metering, and Billing
DB5
DB1
DB3
DB2
DB1
DB6
DB2
DB3
DB1
DB2
DB3
DB4
DB4
DB5
DB1
DB7
Scalability and Availability: Fabric, Failover, Replication, and Load Balancing

Computing EvolutionTowards Shared Resources
Learning to share more
resources over time.
Owned
Isolated
Shared
Pooled
Things we used to want
Exclusively are now a burden…
Disk
Disk
Computer
Disk
Disk
Computer
Memory
Disk
Memory
Time 

SQL Azure Compared To…
Hosted SQL Server
SQL Azure further separates physical and logical administration
SQL Azure includes HA/DR
SQL Azure will include other high level services in the future – e.g. BI, “Data Hub”, etc.
SQL Server On Premises
Separates logical/physical administration
Provide DBMS “Utility”
Ultimately  Write your app and deploy to: SQL Server, SQL Server Utility, SQL Azure, etc.

Sample of SQL Compatibility
Included in v1
Tables, indexes and views
Stored Procedures
Triggers
Constraints
Table variables, session temp tables (#t)
…
Out of Scope for v1
Distributed Transactions
Distributed Query
CLR
Service Broker
Spatial
Physical server or catalog DDL and views

High Level Architecture
SQL Data Services Gateway Tier
Protocol Parser
Protocol Parser
Protocol Parser
Protocol Parser
Protocol Parser
Protocol Parser
Protocol Parser
Management Services
Management Services
Management Services
Management Services
Management Services
Management Services
Management Services
Partition Services
Partition Services
Partition Services
Partition Services
Partition Services
Partition Services
Partition Services
SQL Data Services Back End
SQL Server
SQL Server
SQL Server
SQL Server
SQL Server
SQL Server
SQL Server
Distributed Data Fabric
Mgmt. Services
Mgmt. Services
Mgmt. Services
Mgmt. Services
Mgmt. Services
Mgmt. Services
Mgmt. Services

SQL Azure Network Topology
Application
Applications use standard SQL client libraries: ODBC, ADO.Net, …
TDS (tcp:1433)
Load balancer forwards ‘sticky’ sessions to TDS protocol tier
Load Balancer
TDS (tcp: 1433)
Gateway
Gateway
Gateway
Gateway
Gateway
Gateway
Data Node
Data Node
Data Node
Data Node
Data Node
Data Node
TDS (tcp: 1433)
Scalability and Availability: Fabric, Failover, Replication and Load balancing

SQL Azure Application Architectures
SQL Azure access from outside MS Datacenter
(On-premises – ADO.NET)
SQL Azure access from within MS Datacenter
(Azure compute – ADO.NET)
App Code / Tools
Application/ Browser
SOAP/REST
HTTP/S
ADO.NET Data Svcs/REST - EF
HTTP/S
App Code
(ASP.NET)
Windows Azure
T-SQL (TDS)
T-SQL (TDS)
SQL Azure
SQL Azure
Code Far
Code Near

SQL AzureUsing one or multiple databases
SQL Data Services
Database
Application
Database
Database
Application
Database

Scalability
Database max size
1 GB (Web Edition)
10 GB (Business Edition)
50 GB (Beta)
SQL Azure scalability
Application must build custom partition logic

Sharding
Scaling data between different databases
SQL Azure dynamic database creation
Partitioning schemas
Vertical
Horizontal
Dynamic
Random
Based on ranges

Sharding
ASP.Net
Application
Customer 123
Partition
Aware
App Tier
Data
Partitions
“Shards”

Sharding Schema

SQL Azure - Pros
Transactions within the platform are not charged
Supports relational data & stored procedures etc.
Supports ACID characteristics of transaction across multiple entities/tables (but not across databases)

SQL Azure - Considerations
Doesn’t provide scalability out of the box and there is a hard limit of 50 GB per database instance. Application need to handle the partition logic
Since application has to build custom partition logic might incur sizable efforts to build such functionality

SQL Azure Improvements
MARS (Multiple Active Results Sets), which simplifies the application design process
ALTER rename process for symmetry in renaming databases
Application and Multi-server management for Data-tier Applications which further streamlines application design and enables deployments of database applications directly from SQL Server 2008 R2 and Visual Studio 2010 to SQL Azure for database deployment flexibility
SQL Azure implements Open Data Protocol

The Future
Ultimately not about “here or there”
Hybrid applications & scenarios
Major scenario & application evolution over next 3-5 years
Constrained by: Trust & Capabilities
Policy based management & execution crucial
Lot of noise/confusion over interop

Summary
Key Takeaways
Microsoft will have a strong position in Cloud business software
SQL Azure is different than SQL Server and hosted SQL Server
SQL Azure will open up new scenarios and opportunities
Think about services / scenarios that have no “on-premises” equivalent

Links
http://comunidadwindows.org
http://ecastrom.blogspot.com
http://www.sqlazurelabs.com
http://www.microsoft.com/windowsazure/
http://sql.azure.com/

© 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 Azure the database in the cloud

by Eduardo Castro on May 07, 2010

Accessibility

Categories

Tags

Upload Details

Usage Rights

2 Embeds 12

Statistics

SQL Azure the database in the cloud — Presentation Transcript

http://www.slideshare.net	11
http://webcache.googleusercontent.com	1