Shared Lower cost Hybrid Azure SQL Database Virtualized Databases Dedicated Higher cost SQL Server in Azure VM Virtualized Machines SQL Server Private Cloud Virtualized Machines SQL Server Physical Machines High Control | High.
Download ReportTranscript Shared Lower cost Hybrid Azure SQL Database Virtualized Databases Dedicated Higher cost SQL Server in Azure VM Virtualized Machines SQL Server Private Cloud Virtualized Machines SQL Server Physical Machines High Control | High.
Shared Lower cost Hybrid Azure SQL Database Virtualized Databases Dedicated Higher cost SQL Server in Azure VM Virtualized Machines SQL Server Private Cloud Virtualized Machines SQL Server Physical Machines High Control | High Maintenance Low Control | Low Maintenance SQL Server in Azure VM Azure SQL Database You access a VM with SQL Server You access a DB You manage SQL Server and Windows: High Availability, Backups, Patching DB is fully managed: High Availability, Backups, Patching You can run any SQL Server version and edition Runs latest SQL Server version, based on Enterprise edition Full on-premise compatibility Incomplete on-premise compatibility (e.g. no jobs, linked servers, FileStream) 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) Different DB sizes: Basic (2GB, 5tps) to Premium (500GB, 735tps) DB availability SLA: 99.99% 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 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) 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) 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 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.. • 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 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 Use the Deployment Wizard (SQL Server 2014 Management Studio) Can be used on previous SQL Server versions Migrates a DB from on-premise to an existing/new Azure VM 1. Backup DB to a network share 2. Copy backup to Azure Storage 3. Provision new VM or select existing VM 4. Restore DB on VM 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 Witness VM P S VM S P VM • 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 • SSD support for TempDB and Buffer Pool Extensions • D-Series VMs come with SSDs (up to 800GB) • SSDs provide high throughput (~32,000 IOPs) at low latency (<1ms) • Improve performance of SQL workloads That use TempDB heavily • That don’t fit in memory • 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 = <size> [ KB | MB | GB ] ) 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-DollarsScale-Quickly/710000004206 Toyota http://www.microsoft.com/casestudies/Microsoft-SharePoint-Server-2013/Toyota/Toyota-Redesigns-Web-Portal-Using-Scalable-Cloud-andContent-Management-Solutions/710000002833 Registro Único de Vivienda: https://customers.microsoft.com/Pages/CustomerStory.aspx?recid=8096 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