SQL Azure By Abhay Parekh Microsoft 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
Introducing Microsoft SQL Azure Database Relational Database as a services Self-managed Easy provisioning and deployment Auto High availability and fault tolerant Self-managing and self-healing Elastic Scale Database as a utility with pay as you grow scaling Rely on Businessready SLAs Enable multi-tenant solutions Manage multiple servers Developer Agility 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
Benefits of SQL Azure Database Differentiated 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
Windows Azure Storage Account User creates a globally unique storage account name Choose geo-location to host storage account
Database Replicas DB! Replica 1 Replica 2 Replica 3 Replica 4
SQL Azure Data Sync Service SQL Azure SQL Azure Sync Group SQL Azure Benefits Scale-out read or read/write Geo replication of data Edge network data distribution
DBA role places more focus on logical management 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
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 Account Server Database 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
Behind the Scenes of SQL Azure Application Apps use standard SQL client libraries: ODBC, ADO.Net, PHP, Internet TDS (tcp) LB Load balancer forwards sticky sessions to TDS protocol tier TDS (tcp) TDS (tcp) SQL Gateway Gateway Gateway Gateway Gateway Gateway Gateway: TDS protocol gateway, enforces AUTHN/AUTHZ policy; proxy to backend SQL SQL SQL SQL SQL SQL Scalability and Availability: Fabric, Failover, Replication, and Load balancing
Customer Scenarios Departmental Applications Web Applications ISV LOB Applications Data Hubs
Database as a service Elastic Scale Easy to Scale out across multiple database. Pay-as-you-grow databases No hardware, physical DB or file management required Multi-tenant data hosting Logical schema per tenant with isolated physical storage Provision new tenants quickly and easily Business-Ready SLAs Reliability Security management across multiple databases
Application Topologies From Windows Azure From Outside Microsoft Datacenter From Outside Microsoft Datacenter & Windows Azure Application / Browser App Code / Tools SQL Server App Code / Tools Windows Azure Microsoft Datacenter Microsoft Datacenter SQL Azure Data Sync Windows Azure Microsoft Datacenter SQL Azure SQL Azure SQL Azure Code Near Code Far Hybrid
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)
Low Transactional Requirements High What are your application s requirements? Storage and Transactional throughput Partitioned Data Partitioning based on Application Requirements (IOPS) Partitioned Data Partitioning based on Application Requirements (IOPS, Storage or both) Low Single Database No Partitioning Storage Requirements Partitioned Data Partitioning Based on Application Requirements (Storage) High
Project Houston
Stay in touch: - Cell No-9969084555 Email-Abhay.Parekh@msptechrep.com Orkut-Search for MSP Abhay Parekh Facebook-Search for MSP Abhay Parekh Twitter-www.twitter.com/parekhabhays Blog-www.microsoftwindows7.blog.co.in
Thank you for suggestions, please email at community@peoplewareindia.com