2. Low Control | Low Maintenance Shared Lower cost Dedicated Higher cost High Control | High Maintenance Hybrid On premises Off premises SQL Server Physical Machines SQL Server Private Cloud Virtualized Machines SQL Server in Azure VM Virtualized Machines Virtualized Databases Azure SQL Database Cloud

3. SQL Server in Azure VM You access a VM with SQL Server You manage SQL Server and Windows: High Availability, Backups, Patching You can run any SQL Server version and editionFull on-premise compatibility Different VM sizes: A0 (1 core, 1GB mem, 1TB) to A16 (16 cores, 112GB mem, 16TB), D-Series (with SSDs) VM availability SLA: 99.95%: Can achieve higher availability (~99.99%) configuring AlwaysOn Reuse on-premise infrastructure (e.g. Active Directory) Azure SQL Database You access a DB DB is fully managed: High Availability, Backups, Patching Runs latest SQL Server version, based on Enterprise edition Incomplete on-premise compatibility (e.g. no jobs, linked servers, FileStream) Different DB sizes: Basic (2GB, 5tps) to Premium (500GB, 735tps) DB availability SLA: 99.99% -Build new apps -Tens to hundreds of DBs -Build new apps -Tens to hundreds of DBs -Migrate existing apps -A few SQL Servers -Migrate existing apps -A few SQL Servers

4.  VMs hosted on Microsoft Azure Infrastructure (“IaaS”) From Microsoft images or your own images Fast provisioning (~10 minutes) Accessible via RDP and Powershell  Pay per use Per minute (only when running) Cost depends on size and licensing Large discounts for MSDN subscribers! You can use your existing SQL licenses Network: only outgoing (not incoming) Storage: only used (not allocated)  Elasticity 1 core / 2GB mem / 1TB   16 cores / 112 GB mem / 16TB

5.  Every VM disk is a BLOB in Azure Storage  3 sync local copies No data loss Highly available (transparent to VM)  3 more async remote copies (if geo-replication enabled) For disaster recovery (manually managed by Microsoft)

6.  SLA: No data loss If VM becomes unavailable, restart in another host  SLA: 1 of 2 VMs in Availability Set: 99.95% (<22 min downtime p/month) Includes Planned downtime due to (monthly) host OS servicing Unplanned downtime due to physical failures Doesn’t include servicing of guest OS or software inside (e.g. SQL)

7.  Over the Internet Public endpoints  Over a site-to-site tunnel Secure tunnel Extend on-premise network to Azure Can join Azure VMs to on-premise domain VPN Device / Windows Server RRAS

8.  Many SQL versions supported SQL 2014 (Enterprise / Standard / Web) SQL 2012 (Enterprise / Standard / Web) SQL 2008 R2 (Enterprise / Standard / Web)  Optimized images Transactional Processing or Data Warehousing Implement multiple optimizations (e.g. storage pools with multiple disks, best stripe sizes, disk caching, SQL traceflags) (Almost) 100% compatibility SQL Failover Clusters coming soon..

10. Lift & Shift Easily move an existing app to Azure infrastructure Without changes (multiple versions of SQL and Windows available) As needed (multiple VM sizes, pay per use)  Dev/Test Build and test new apps using the latest versions of SQL Server and Windows Hybrid Integrate SQL Server on Azure with your existing infrastructure or apps Active Directory (Windows Authentication / IT policies) Use SQL Server(s) in Azure VMs as replicas of on-premise SQL Servers Disaster Recovery Read workloads / backups

11. Use a Gallery image Includes everything you need Engine Reporting Services Analysis Services Integration Services Management Studio Refreshed monthly with latest fixes Bring your Own Image Create a VHD (sysprep) Upload to your Azure Storage account Provision VM from VHD

14.  SQL Server High Availability Configure an AlwaysOn Availability Group between VMs in the same region Automatic failover on SQL/VM issues (~10 seconds) Easily configurable using AlwaysOn Portal Template SS PP PP SS VM Witness

16. SQL Server Disaster Recovery Configure an AlwaysOn Availability Group between VMs in different regions Manual Failover (~15 seconds). Test it at any time! Using Internal Endpoints

17. USE MASTER GO ALTER DATABASE tempdb MODIFY FILE (NAME= tempdev, FILENAME= 'D:\tempdb.mdf') GO ALTER DATABASE tempdb MODIFY FILE (name = templog, filename = 'D:\templog.ldf') GO USE MASTER GO ALTER DATABASE tempdb MODIFY FILE (NAME= tempdev, FILENAME= 'D:\tempdb.mdf') GO ALTER DATABASE tempdb MODIFY FILE (name = templog, filename = 'D:\templog.ldf') GO ALTER SERVER CONFIGURATION SET BUFFER POOL EXTENSION ON ( FILENAME = 'D:\ExtensionFile.BPE', SIZE = [ KB | MB | GB ] )

18. GE Healthcare https://customers.microsoft.com/Pages/CustomerStory.aspx?recid=12166 Blinkbox: http://www.microsoft.com/casestudies/Microsoft-Azure/blinkbox/Movie-Streaming-Business-Uses-Cloud-Service-to-Save-Millions-of-Dollars- Scale-Quickly/710000004206http://www.microsoft.com/casestudies/Microsoft-Azure/blinkbox/Movie-Streaming-Business-Uses-Cloud-Service-to-Save-Millions-of-Dollars- Scale-Quickly/710000004206 Toyota http://www.microsoft.com/casestudies/Microsoft-SharePoint-Server-2013/Toyota/Toyota-Redesigns-Web-Portal-Using-Scalable-Cloud-and- Content-Management-Solutions/710000002833http://www.microsoft.com/casestudies/Microsoft-SharePoint-Server-2013/Toyota/Toyota-Redesigns-Web-Portal-Using-Scalable-Cloud-and- Content-Management-Solutions/710000002833 Registro Único de Vivienda: https://customers.microsoft.com/Pages/CustomerStory.aspx?recid=8096 https://customers.microsoft.com/Pages/CustomerStory.aspx?recid=8096

19. SQL Server on Azure VM http://azure.microsoft.com/en-us/services/virtual-machines/sql-server/ Documentation http://msdn.microsoft.com/en-us/library/azure/jj823132.aspx