SQL On Azure Parikshit Savjani, Sr. Premier Field Engineer

About Me 7 Years Sr. Premier Field Engineer @talktosavjani http://www.sqlserverfaq.net

Agenda SQL in Azure Overview SQL on Azure VM(IaaS) Azure SQL Database (PaaS) Decision Matrix

SQL in Azure Overview © 2012 Microsoft Corporation Microsoft Confidential

Microsoft Azure Offerings

Motivation For SQL Server on Azure Low Hardware & Data Center Costs Low Administration Costs Elastic Scale Low turnaround time for setup & configuration Enterprises now has four options to host SQL Server in environment SQL Server on Physical Machines SQL Server on VMs in DataCenters SQL Server on Azure VMs (IaaS) SQL Server on Azure SQL Database (PaaS) Goals

SQL on Azure VMs (IaaS) © 2012 Microsoft Corporation Microsoft Confidential

Guiding principles No more Storage Admin Follow Best Practices 11/8/2018 Guiding principles No more Storage Admin Follow Best Practices Local is good -- Courtesy Amit Banerjee & Sourabh Agrawal © 2015 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Storage Account Storage account limit: 20,000 IOPs Data Disk limit: 500 IOPs (for 8KB on Standard tier and above) Be aware of Ingress/Egress limits Caching policy = NONE for data disks Disable GEO-replication on storage account -- Courtesy Amit Banerjee & Sourabh Agrawal 11/8/2018

AZURE PREMIUM STORAGE > 50,000 IOPS per VM Persistent SSD storage 11/8/2018 AZURE PREMIUM STORAGE > 50,000 IOPS per VM Persistent SSD storage 64TB of storage <1 ms latency for read operations -- Courtesy Amit Banerjee & Sourabh Agrawal © 2015 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

SQL Optimization on Azure SQL Server SSD drives for tempdb or BPE on D-Series ONLY Separate data disks for data and log files Windows Change column count to appropriately 64-KB allocation unit size Use Storage Spaces or OS striping -- Courtesy Amit Banerjee & Sourabh Agrawal 11/8/2018

SQL Best Practices on Azure 11/8/2018 SQL Best Practices on Azure SQL Server Use Lock Pages In Memory Enable instant file initialization Database Disable autoshrink & Avoid autogrow Use database page compression Backup to URL with compressed backups -- Courtesy Amit Banerjee & Sourabh Agrawal 11/8/2018 © 2015 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Azure SQL Database (PaaS) © 2012 Microsoft Corporation Microsoft Confidential

Basic Standard Premium Availability SLA 99.99%* Security Auditing Scalability Elastic Scale, client-side scale out (preview) Point-in-time Restore Any point within 7 days Any point within 14 days Any point within 35 days Business Continuity Geo-Restore Standard Geo-Replication Active Geo-Replication Database Max Size 2 GB 250 GB 500 GB V2 servers Database Throughput Units Basic: 5 S0: 10 S1: 20 S2: 50 P1: 100 P2: 200 P3: 800 Available tiers (~$/month) Billed hourly Basic: $4.99 S0: $15 S1: $30 S2: $75 P1: $465 P2: $930 P3: $3720 V12 servers S3: 100 P1: 125 P2: 250 P3: 1000 S3: $150 SQL Server compat Near 100%

Azure SQL Database v2 Azure SQL Database v12

Next Generation Azure SQL DB (V12) 11/8/2018 Next Generation Azure SQL DB (V12) The Theme for the new update T-SQL syntax at par or comparable with SQL 2014 New architecture SQL core engine upgraded from SQL 2012 to SQL 2014++ © 2015 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Restore to point of deletion 11/8/2018 Data Protection Disaster Recovery Geo-Replication Geo-Restore Geo-Redundant Backup RPO < 1 hour Recovery Time Minutes to Hours Included for *all* databases Asynchronous replication to a regional Data center RPO < 5 seconds Recovery Time < 30 seconds Available for Standard & Premium Oops Recovery Point in time restore (PITR) Continuous backup with tiered retention period Restore to any-point Recovery Time Minutes to Hours Included for *all* databases Tail-end backup Restore to point of deletion Recovery Time Minutes to Hours Accidental Database deletion © 2015 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Sharding and Tenancy Models (Elastic Scale) Single-tenant per database DB1 Customer 1 DB2 Customer 2 … Single tenant per database Each tenant’s data is stored in a different DB Multiple tenants per database Multiple tenants share the same DB Hybrid model Some tenants share databases, others get their own Temporal model Sharding based on date/time Most recent shard constantly receives newly arriving data Multi-tenant per database DB1 Customer 1 Customer 2 Customer 3 DB2 Customer 4 Customer 5 Customer 6 …

Decision Matrix © 2012 Microsoft Corporation Microsoft Confidential

Where to host my SQL Database? (Decision Matrix) Physical Server Virtualization (Private Cloud) Azure VMs (IaaS) Azure SQL Database SQL Support Any SQL version Any SQL version Any SQL Version SQL Azure Database v12 Data Privacy Highly Sensitive Highly Sensitive Sensitive Sensitive Network Performance Application Performance impacted minimally by LAN Application Performance dependent on Network Performance(ExpressRoute) Storage Performance Determined by On-Premise Storage Team 500-50K IOPs per Data Disk Self-Managed Backup Strategy 3rd party SQL backup Solutions\Azure Storage Azure Storage Builtin Automatic Backup Resources Winserv/Storage/DBA/Application Teams Winserv/DBA/Application Team DBA/Application Team Cost Hardware & Admin Cost Lower Hardware & High Admin Cost Lower Hardware & Admin Cost Minimum Cost Best For Mission Critical, High Performance, Highly Sensitive Data Apps Dev\Cert\Sensitive Data Apps New Cloud Designed Apps

Azure Database (PaaS) v/s SQL on Azure VMs (IaaS) Azure SQL Database (PaaS) SQL Server in Azure VM (IaaS) Best for New cloud-designed applications that have time constraints in development and marketing. Suited for Software-as-a-Service applications. Existing Dev Cert & test environments applications that require fast migration to the cloud with minimal changes & you do not want to buy on-premises nonproduction SQL Server hardware. SQL Server applications that require accessing on-premises resources (such as, Active Directory) from Azure via a secure tunnel. Rapid development and test scenarios when Disaster recovery for on-premises SQL Server applications using backup on Azure Storage or AlwaysOn replicas in Azure VMs. SQL Support Near SQL Like Functionality in preview. Application should be supported on Azure SQL Database. Existing environments cannot be migrated to Azure Database unless application is rewritten. All SQL versions (SQL 2005 – SQL 2014) are supported similar to on-premise functionality. Existing applications can be migrated with minimal coding effort Size Constraints Databases of up to 500 GB in size. Database Any Size Resources SQL Azure Database can be provisioned by the DBA Team after which there is minimal intervention & Support from DBA Teams. Winserv Team governs the VMs images while DBA Team governs the SQL setup, administration & support similar to current SQL environment Total cost of ownership Eliminates hardware costs. Reduces administrative costs. Eliminates hardware costs. Business continuity In addition to built-in fault tolerance infrastructure capabilities, Azure SQL Database provides features, such as Point in Time Restore, Geo-Restore, and Geo-Replication to increase business continuity. For more information, see Azure SQL Database Business Continuity. SQL Server in Azure VM lets you to set up a high availability and disaster recovery solution for your database’s specific needs. Therefore, you can have a system that is highly optimized for your application. You can test and run failovers by yourself when needed. For more information, see High Availability and Disaster Recovery for SQL Server in Azure Virtual Machines. Hybrid cloud Your on-premises application can access data in Azure SQL Database. But from SQL Database we can’t access resources on-premise With SQL Server in Azure VMs, you can have applications that run partly in the cloud and partly on-premises. For example, you can extend the on-premises network and Active Domain Directory to the cloud via Azure Network Services. In addition, you can store on-premises data files in Azure Storage using the SQL Server Data Files in Azure feature. For more information, see Introduction to SQL Server 2014 Hybrid Cloud.

Premier Field Engineer pariks@Microsoft.com Contact Parikshit Savjani Premier Field Engineer pariks@Microsoft.com http://www.sqlserverfaq.net © 2012 Microsoft Corporation Microsoft Confidential

References Public Links Azure Pricing Calculator Pricing Overview Getting started with a SQL Server VM on Azure Setting up a SQL Azure VM Whitepaper: Performance Guidance for SQL Server VMs Azure Subscription Limits Azure Scalability and Performance Targets Some FAQs on Azure networking MSFT ONLY Links SQL on Windows Azure Virtual Machine Wiki SQL Server on Azure – Data Services 11/8/2018