Fast Start for Microsoft Azure – SQL Server IaaS Workshop

Section 1: Cloud Database Deployment Options Lesson 1: Introduction to IaaS, and PaaS Understanding the difference between IaaS and PaaS After completing this lesson, you will be able to understand: The reason to implement HADR solutions Why should you learn this material? It will provide you a good understanding of why HADR solution is required

Cloud Database Deployment Virtual SQL Server in Private Cloud Deploy mission critical SQL installation in Virtualized Machines + Appliances Cloud Database Deployment IaaS Migrate existing SQL private cloud workload to cloud-hosted virtual machines SQL Server on Microsoft Azure Virtual Machines PaaS Take advantage of massive computational resources of Microsoft Azure SQL Database service Microsoft Azure SQL Database 9/16/2018

SQL Server Cloud Continuum Low Control Shared Lower cost Dedicated Higher cost High Control Hybrid Cloud Physical Virtual PaaS SaaS IaaS On premises Off premises SQL Server Physical Machines (raw iron) SQL Server Private Cloud Virtualized Machines+ Appliances SQL Server in WA VM Virtualized Machines Database Services SQL Server Cloud Continuum Microsoft Azure SQL Database

Microsoft Azure Virtual Machines (IaaS) IaaS introduces new functionality that allows full control and management of both Windows and Linux virtual machines along with an extensive virtual networking Offering. Flexible Open Solid Easily migrate existing applications as-is to the cloud Assist new cloud app development by Integrating IaaS and PaaS functionality Set up new Virtual Machines in Microsoft Azure with only a few clicks Agentless deployment for Windows Servers Start from a pre-built image from our image library Upload your own virtual hard disk from on-premises Create your own customized images Support for community and commercial versions of Linux Move images back on premises as necessary Run enterprise applications such as SQL Server, SharePoint, or AD DS in the cloud Easily create hybrid cloud and on-premises Solutions with virtual private network (VPN) connectivity between the Microsoft Azure data center and your own network Key point is – It’s just a virtual machine, a container for any software (operating system all the way up) you want to run in it. You pay for the underlying resources you are reserving (CPU and RAM). These virtual machines (using virtual networking) can be private to your corporate network – they can see your corporate AD DS and so forth). Even though they live in the public cloud, you can surround and protect them so they are just part of your own infrastructure.

IaaS Workloads: It’s All About the App Line of Business Applications: Custom Applications Customer Relationship Management (CRM) Content Management System (CMS) Enterprise Resource Planning (ERP) Business Intelligence (BI) Application infrastructure: File servers Databases Identity Source control Developer, testing and staging environments: Quickly provision and un-provision entire environments Hybrid applications: Applications that span your data center and the cloud Useful scenarios for IaaS

Avoiding Lock-In Windows Virtual Machines can move freely between all three clouds. Microsoft Azure Other Service Providers Hyper-V Virtual Machine In this slide, the important thing to land is that our virtual machine implementation is the same as on-premises. Now we only do Hyper-V (there are third-party tools and tools in System Center that can convert between VMWare and Hyper-V), but it is simple to take existing Hyper-V images and move to the cloud, to other hosters who host Hyper-V or Microsoft Azure – and of course you can move them back as well. Note: You cannot do this with Amazon Web Services (AWS) – you are locked in. Customer Data Center

Flexibility of Azure IaaS Support for existing and new virtualized workloads on Azure. Multiple Ways to Get Started Variety of Images to Select Persistent in Storage Boot Virtual Machine from New Disk Management Portal >_ Blob Storage Scripting (Windows, Linux, and Mac) Cloud Representational state transfer (REST) API

SQL Server and Azure SQL Database Public Cloud Delivery Options SQL Server in a Microsoft Azure Virtual Machine Microsoft Azure SQL Database (Formerly SQL Azure Database) Move Existing Tier Two and Three Apps Develop and Test Backup Database to the Cloud Extend On-Premises Apps to Microsoft Azure Virtual Machine Develop New Cloud-Designed Apps Extend On-Premises Apps to Microsoft Azure SQL Database Key Scenarios At this point we covered compute. Remember our key building blocks (Compute, Data Services, Networking, and Application Services). Outside of compute (which is special in that this is where your custom code and business logic runs), all these other capabilities in the platform are things that your applications just use. Of course, any given app won’t use all of these services, most will just use a few. The point is that we have a tremendously complete platform. Check if the briefing also has a SQL Azure topic (which will usually follow the Microsoft Azure topic). If so, just cover this very lightly. Most apps though do need to store or deal with structured data. Typically that would live in a database. There are two flavors we are going to talk about – SQL Server in a virtual machine, and Azure SQLDB. This is also a good proxy or illustration that makes things very real between the differences of IaaS and PaaS and how all the value and promise of the cloud is delivered through PaaS (and just some of it through IaaS). Can Use both SQL Server in Microsoft Azure Virtual Machine and Microsoft Azure SQL Database in a single app.

Azure SQL DB - How It Works Infrastructure Layer PHP Windows Communication Foundation (WCF) Data Services SQL Server Applications and Tools Open Database Connectivity ADO.NET Tabular Data Stream (TDS) Client Layer Services Layer Provisioning Billing and Metering Connection Routing … TDS and Secure Socket Layer Platform Layer SQL Database Fabric Management Services Architecture Client Layer: Used by the application to communicate directly with the SQL database. Services Layer: Gateway between the client layer and the platform layer. Platform Layer: Includes physical servers and services that support the services layer. Infrastructure Layer: IT administration of the physical hardware and operating system. S Fault Domain One Azure SQL Database Web Site Of course Azure SQL DB is somewhere under the covers, SQL Server. This picture illustrates where SQL Server actually lives. There are a number of services built around this that really add value to the picture and deliver those cloud principles (scale, elasticity, self-service, resilience, and so forth). You don’t need to explain all the layers – the point is they are there and actually that in the traditional IT world, many of these functions in the picture are done by people, by IT pros and database administrators, worrying about how to get databases provisioned, keep them running, change them, fix them when broken, and so forth. Click: The other interesting thing about this picture is that when you provision a database for your app (which you can do in about six seconds), the app actually gets three virtual databases and one logical database that it interacts with (click). Each of the three database is located within Microsoft Azure in fault domains – a unit of computers all with redundant hardware, racks, switches, and so forth. There is a primary and two secondaries. Microsoft Azure is responsible for all the consistency and integrity of the three databases and, completely automated, will recover from failures and ensure balance of primaries and secondaries across physical nodes. All you need to do is provision a database, say how big you want it, upload your schema and data, then start using it. Everything else is taken care of for you. And, you only pay for the actual data you are storing in the database (calculated on a daily basis). Contrast this picture against doing your own thing in Azure Virtual Machines with SQL Server (or any other database for that matter), and of course having to provide the same level of resilience. P Fault Domain Two S Fault Domain Three

Azure SQL Database (V12) Premium V12 Performance Improvements A step towards closing the T-SQL compatibility gap between Azure SQL database and SQL Server Better premium performance New architecture SQL core engine upgraded from SQL Server 2012 to SQL Server 2014+ New Capabilities such as Row-Level Security, TDE for SQL DB, SQL Audit, Dynamic Data Masking, Full Text Search, online indexing, Columnstore Indexes and Azure SQL Database Query Store (Premium tier only) and other capabilities (many in Preview and based on region) Presenter Note: A key point is that Azure SQL Database is part of the cloud first model in that you get to peer into the future to many of the features making its way eventually to the box product. Premium V12 Performance Improvements Higher DTU rating for Premium V12 DBs Runs on Gen3/Gen4 HW Up to 100x query performance improvement with Compression and In- memory Columnstore Indexes More IO Throughput for premium databases 10x more read IOs Fast SSDs More Transaction log throughput Improved replication efficiency for better write throughput More transaction log bandwidth available for premium databases Over 2x improvement in log throughput What’s New in Azure SQL Database (V12) https://azure.microsoft.com/en-us/documentation/articles/sql-database-v12-whats-new/

Who Manages What? Infrastructure (IaaS) Microsoft manages hardware and virtualization technology Platform (PaaS) Microsoft manages everything except your applications and data On-demand data centers, also known as IaaS, provide compute power, memory, and storage, typically priced per hour, based on resource consumption. You pay only for what you use, and the service provides all the capacity you need, but you are responsible for monitoring, managing, and patching your on-demand infrastructure. The biggest advantage of IaaS is that it offers a cloud-based data center without requiring you to install new equipment or to wait for the hardware procurement process. This means you can get IT resources that otherwise might not be available.

IaaS Vs PaaS Full features of on premise SQL Server and BI SQL Server Integration Services (SSIS) SQL Server Analysis Services (SSAS) SQL Server Reporting Services (SSRS) Full control over physical administration data files Easier migration path to the cloud for existing code Free from physical administration and management Quick provisioning for testing and POC; focus on the code Elasticity with features like self-sharding and Data Sync 9/16/2018

Lesson Knowledge Check Question: What are the two ways of deploying SQL Server databases to Azure? Answer: SQL Server in a virtual machine, and Azure SQLDB Question: What features of SQL Server does SQL Server on IaaS provide ? Answer: Full features of on premise SQL Server and BI © 2015 Microsoft Corporation