SQL AzureBy
Abhay ParekhMicrosoft Corporation
Leverage this
Presented by : -
Abhay S. Parekh
MSP & MSP Voice Program Representative,
Microsoft Corporation.
Before i begin…
Demo
Let‟s “understand”
SQL Azure now
SQL Azure is…
• Cloud based RDB
• For Azure
• Built on SQL Server Technology
• No need to deploy, manage, patch etc.
• High Availability and Fault Tolerant
• Supports T-SQL
• Backup and recovery, geo-distribution and disaster
recovery are built-in
We‟re talking about…
Or more precisely
Easy provisioning and deployment
Auto High availability and fault tolerant
Self-managing and self-healing
Database as a utility with pay as you grow scaling
Rely on Business-ready SLAs
Enable multi-tenant solutions
Manage multiple servers
Build cloud-based database solutions on a familiar relational model
Build on existing developer skills and familiar Transact-SQL syntax
Explore new data application patterns
Elastic Scale Developer AgilitySelf-managed
Introducing Microsoft SQL Azure DatabaseRelational Database as a services
Benefits of SQL Azure DatabaseDifferentiated value proposition – Database as a service
Symmetry with Traditional RDBMS
Familiar T-SQL relational model
Support existing code libraries and protocols
Ecosystem of familiar development and management tools
Differentiated value
No physical administration
Low-friction provisioning
Easy scale-out
Multi-tenant
Self-management
Automatic HA and DR
User creates a globally unique storage account name
Choose geo-location to host storage account
Windows Azure Storage Account
Database Replicas
Replica 1
Replica 2
Replica 3
DB
Replica 4
!
SQL Azure Data Sync Service
Benefits
• Scale-out read or read/write
• Geo replication of data
• Edge network data distribution
Sync
Group
SQL
Azure
SQL
AzureSQL
Azure
Logical vs. Physical Administration• SQL Azure focus on logical administration
– Schema creation and management
– Query optimization
– Security management (Logins, Users, Roles)
• Service handles physical management– Automatically provides HA “out of box”
– Transparent failover in case of failure
– Load balancing of data to ensure SLA
DBA role places more focus on logical management
Security Model• Uses regular SQL security model
– Authenticate logins, map to users and roles
– Authorize users and roles to SQL objects
• Support for standard SQL Auth logins– Username + password
Security model is 100% compatible with on-premise SQL
Service Provisioning Model• Each account has zero or more logical
servers– Provisioned via a common portal
– Establishes a billing instrument
• Each logical server has one or more
databases– Contains metadata about database & usage
– Unit of authentication, geo-location, billing, reporting
– Generated DNS-based name
• Each database has standard SQL objects– Users, Tables, Views, Indices, etc
– Unit of consistency
Account
Server
Database
Behind the Scenes of SQL AzureApplication
Internet
LBTDS (tcp)
TDS (tcp)
TDS (tcp)
Apps use standard SQL client libraries:
ODBC, ADO.Net, PHP, …
Load balancer forwards „sticky‟ sessions
to TDS protocol tier
Gateway Gateway Gateway Gateway Gateway Gateway
Scalability and Availability: Fabric, Failover, Replication, and Load balancing
SQL SQL SQL SQL SQLSQL
Gateway: TDS protocol gateway, enforces AUTHN/AUTHZ policy; proxy to backend SQL
Customer ScenariosDepartmental Applications Web Applications
Data HubsISV LOB Applications
Elastic ScaleDatabase as a service
Easy to Scale –out across multiple database.
Pay-as-you-grow databases
No hardware, physical DB or file management required
Business-Ready SLAsReliability
Security management across multiple databases
Multi-tenant data hosting
Logical schema per tenant with isolated physical storage
Provision new tenants quickly and easily
Application TopologiesFrom
Windows AzureFrom Outside
Microsoft Datacenter
From Outside
Microsoft Datacenter
& Windows Azure
Application / Browser
Windows
Azure
SQL Azure
Code Near
App Code / Tools
SQL Azure
Microsoft
Datacenter
Code Far Hybrid
Microsoft
Datacenter
SQL Azure
SQL Server
Microsoft
DatacenterWindows
Azure
SQL Azure
Data Sync
App Code / Tools
Connection Model• SQL Azure exposes native SQL Server TDS protocol
• Use existing client libraries
– ADO.NET, ODBC, PHP
• Client libraries pre-installed in Windows Azure roles
• Support for ASP.NET controls
• Clients connect directly to a database
– Cannot hop across DBs (no USE)
What are your application‟s requirements?Storage and Transactional throughput
Storage RequirementsLow High
Transa
ctio
nal R
eq
uirem
ents
Lo
wH
igh
• Single Database
• No Partitioning
• Partitioned Data
• Partitioning Based on
Application Requirements
(Storage)
• Partitioned Data
• Partitioning based on
Application Requirements
(IOPS)
• Partitioned Data
• Partitioning based on
Application Requirements
(IOPS, Storage or both)
Project “Houston”
Stay in touch: -
• Cell No-9969084555
• Orkut-Search for MSP Abhay Parekh
• Facebook-Search for MSP Abhay Parekh
• Twitter-www.twitter.com/parekhabhays
• Blog-www.microsoftwindows7.blog.co.in