Sql azure introduction
0 likes244 views
SQL Azure Database provides SQL Server database technology as a cloud service, addressing issues with on-premises databases like high maintenance costs and difficulty achieving high availability. It allows databases to automatically scale out elastically with demand. SQL Azure Database uses multiple physical replicas of a single logical database to provide automatic fault tolerance and high availability without complex configuration. Developers can access SQL Azure using standard SQL client libraries and tools from any application.
Sql azure introduction
- 1. Oleh : INTRODUCTION Suherman, STP, MCTS, MVP
- 2. On-premises databases are very high-maintenance: Installation, Setup, Patching, Physical Management Achieving High Availability (HA) with a solid Disaster Recovery (DR) or Fault Tolerance (FT) plan is very expensive, usually cost prohibitive Scaling up (or down) quickly is difficult and expensive WHAT'S WRONG WITH MY DATABASE?
- 3. SQL Azure Database is SQL Server database technology delivered as a service on the Windows Azure Platform Ideal for both simple and complex applications Enterprise-ready with automatic support for HA Designed to scale out elastically with demand Get started quickly Choose a plan Choose a billing option Provision servers
- 4. SQL AZURE DATABASE Highly scaled out relational database as a service Relational database service Browser SQL Azure Database (Windows Azure Compute) • SQL Server technology foundation SOAP/REST Astoria/REST - EDM • Highly symmetrical HTTP/S HTTP/S • Highly scaled App Code Database “as a Service” – beyond hosting (ASP.NET) SQL Server Reporting Windows Azure Server Customer Value Props Compute (on-premises) T-SQL (TDS) T-SQL (TDS) Self-provisioning and capacity on demand Symmetry w/ on-premises database SQL Azure platform Database MS Datacenter Automatic high-availability and fault- tolerance Automated DB maintenance (infrastructure) - AD Federation (LiveId /.Net Svcs ACS) Simple, flexible pricing – “pay as you grow”
- 5. SQL AZURE DATABASE Single Logical Multiple Physical Database Replicas Replica 1 Replica 2 DB Replica 3
- 6. SQL AZURE NETWORK TOPOLOGY Applications use standard Application SQL client libraries: ODBC, ADO.Net, PHP, … Internet Azure Cloud TDS (tcp) Security Boundary Load balancer forwards LB „sticky‟ sessions to TDS protocol tier TDS (tcp) Gateway Gateway Gateway Gateway Gateway Gateway Gateway: TDS protocol gateway, enforces AUTHN/AUTHZ policy; proxy to TDS (tcp) CloudDB SQL SQL SQL SQL SQL SQL Scalability and Availability: Fabric, Failover, Replication, and Load balancing
- 8. SYNCHRONIZE YOUR DATA Provisioning synchronization groups Deploy database to hub and clients Set synchronization schedule Set conflict resolution policy Define data set Add SQL Azure clients to topology Install agents on SQL Server clients and add them to topology using keys Deploy topology Operational considerations Manual synchronization supported Hub updates require one synchronization to distribute to all clients Client updates require two synchronizations to distribute to all clients Sync Framework triggers may affect application behavior
- 9. Two sizes available: Web Edition – 1Gb @ $9.99 per month Business Edition – 10Gb $99.99 per month Bandwidth costs: Ingress to cloud - $0.10 per Gb Egress from cloud - $0.15 per Gb Guaranteed 99.9% uptime (down ~44 minutes per month) PRICING AND AVAILABILITY
- 10. DEMONSTRATION Lightning Introduction to SQL Azure and Use
Editor's Notes
- #6: Slide ObjectiveUse this slide to transition into an explanation of SQL Azure Database (Reporting and Data Sync will be covered later)Explain at a high level how SQL Azure worksSpeaker NotesDesign Principle of SQL Azure: Focus on combining the best features of SQL Server running at scale with low frictionSQL Azure is a high availability databaseAlways three transaction consistent replicas of the databaseOne primary replica; two slave replicasFailure of a replica will result in another replica being spun up immediately by the fabricFailure of the primary replica means a slave replica will become the primary and a new slave will spin upMinimal down timeTypically just a few dropped connectionsEasy to code for the failover scenario- if you are ding god connection management and error handling will be fineClustered index required on all tables to allow replicationNotesUseful article from SQL Azure teamhttp://msdn.microsoft.com/en-us/magazine/ee321567.aspx