Setting Up SQL Server on Windows Azure Understanding Options and Differences Stephen Wynkoop, Microsoft SQL Server MVP Founder, SSWUG.ORG
Session Q&A Housekeeping Questions after the fact: swynk@sswug.org Can t cover EVERY question or option
Ch-ch-ch-ch-changes Please Note
Why Consider Azure? Overview Scalability Availability Recoverability Options, options, options
Agenda Setting up your Windows Azure SQL Database (WASD) Setting up a VM Setting up a SQL Server on a VM Understanding some of the differences between VM and WASD implementations Making the choice, questions to ask Best Practices Disaster Recovery considerations in the environments
Initial Considerations Features required Management level desired Platform selection
Virtual machine Platform Selection SQL Server install ala on-premise/hybrid Windows Azure SQL Database
Fundamentals Cloud Architecture can be very different from On-Premise Architecture
Hybrid Cloud
Hybrid Example
Hybrid Benefits Migrations Control Secure/private data requirements Can pick and choose services to best fit your needs Cost control Learning curve management
Questions: Features Required Bandwidth/access level requirements Storage requirements (db size, backup styles) Specific features Encryption Full-text Higher level access to SQL Server, the OS
Questions: Management Level Desired Managed services vs. self-service Fault tolerance automation
Demo - Setting Up: Virtual Machine
Options Matter Information Security & Access Controls The Wallpaper/Management UI Subtle Issues Throttling Easy vs. Right Architecture
WASD Performance Tiers (and performance metrics/objectives) Basic Standard Premium Uptime SLA 99.95%* Database Size Limit 2 GB 250 GB 500 GB Restore Latest restore point within 24 hours Any point within 7 days Any point within 35 days Disaster Recovery (DR) Restore to alternate Azure region** Geo-Replication, passive replica** Active Geo- Replication, up to 4 readable replicas Performance Objectives Transaction rate per hour Transaction rate per minute Transaction rate per second
Choosing Performance Tiers Database Throughput Units (DTUs) a combination of CPU, RAM, Disk that determines overall performance of your database as a platform. Transaction rates shown for each. Basic Standard Premium Basic: 1 DTU 3,467/hour S1: 5 DTU 283/minute S2: 25 DTU 1,470/minute P1: 100 DTU 98/second P2: 200 DTU 192/second P3: 800 DTU 730/second
Demo - Setting Up: WASD
Questions: Disaster Recovery DR can drive some option choices Disaster recovery Point in time recovery Oops recovery Compliance requirements?
Demo DR Options with WASD
Best Practices Don t miss a key point of the cloud Managed scale Reality-based measures and forecasting Get all that touch your server involved Can be surprise features needed Be aware of compliance requirements
Best Practices II Internal expertise may drive some choices Be aware that small charges add up IOPS Storage temporary servers
Best Practices III Moving INTO/OUT of WASD is more painful than a traditional migration Choose wisely.
Summary Outstanding platform Lots of growth and change/releases Will force introspection Architecture, growth, functional requirements Won t remove requirement for admin
Resources Comparing AZURE and SQL Server http://social.technet.microsoft.com/wiki/contents/articles/996.compa rison-of-sql-server-with-azure-sql-database.aspx See TSQL that is NOT WASD SUPPORTED: http://msdn.microsoft.com/en-us/library/ee336253.aspx See TSQL that is PARTIALLY WASD SUPPORTED: http://msdn.microsoft.com/en-us/library/ee336267.aspx Performance Tiers http://blogs.technet.com/b/dataplatforminsider/archive/2014/05/05/ azure-sql-database-service-tiers-amp-performance-q-amp-a.aspx
Questions? Click Session Q&A Email swynk@sswug.org Thanks for watching and thank you for your trust in SSWUG.ORG!