Presentation is loading. Please wait.

Presentation is loading. Please wait.

Microsoft Services 9/19/2018 SQL OLTP on Microsoft Azure Virtual Machines (IaaS) Jumpstart Delivery Training Date of Presentation © 2010 Microsoft Corporation.

Similar presentations


Presentation on theme: "Microsoft Services 9/19/2018 SQL OLTP on Microsoft Azure Virtual Machines (IaaS) Jumpstart Delivery Training Date of Presentation © 2010 Microsoft Corporation."— Presentation transcript:

1 Microsoft Services 9/19/2018 SQL OLTP on Microsoft Azure Virtual Machines (IaaS) Jumpstart Delivery Training Date of Presentation © 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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.

2 Industry Trends and SQL on Cloud OS SQL OLTP on IaaS Jump Start
Objectives Industry Trends and SQL on Cloud OS SQL OLTP on IaaS Jump Start Engagement Delivery 9/19/2018

3 PRIVATE AND PUBLIC CLOUD
DATA EXPLOSION CONSUMERIZATION OF IT PRIVATE AND PUBLIC CLOUD Industry Trends On-premises Virtualized Private Cloud Hosted Digital data will grow 44x over the next decade ( )1 By EOY % of primary databases expected to be virtualized 2 Public cloud services will account for 46% of net-updated growth in IT spending in As we look at the IT industry today, a number of important trends are changing the way software is being purchased, deployed and used in the organization. Data Explosion The volume of data in the workplace is exploding. According to IDC, digital data will grow more than 40x over the next decade. As more and more data is created digitally, we expect to see ever greater demands being placed on our data platforms to store, secure, process and manage these large volumes of data. Consumerization of IT Today we see an increasing trend toward the “consumerization” of IT—creating the demand for Web 2.0 experiences in the business environment. As consumers, we are accustomed to powerful user-friendly experiences, whether searching the Internet on a mobile device to find information instantly, or quickly accessing our personal financial data. In the workplace, however, we are often unable to answer even the most basic questions about our business. Increasingly, users demand business experiences that more closely mirror the convenience and ease of use in consumer life. Infoweek reference: flux/d/d-id/ Summary of article: impac/ Private and Public Cloud Cloud computing is changing the way data is accessed and processed, and it is creating whole new models for the way applications are delivered. According to IDC, Cloud services will account for 46% of net-new growth in overall IT spending. With private and public cloud infrastructure, organizations have an opportunity to reduce TCO dramatically as data volume increases. As we see an evolution toward greater use of private and public clouds, we see an increasing need for solutions that support hybrid cloud scenarios. 1 IDC Digital Universe Study, sponsored by EMC, May 2010. 2 Information Week 2012 State of Database Technology Survey of 760 business technology professionals 3 IDC, Worldwide and Regional Public IT Cloud Services 2011 – 2015 Forecast, Doc #228485, June 2011 9/19/2018

4 Cloud Database Deployment
Virtual Deploy mission critical SQL installation in Virtualized Machines + Appliances SQL Server in Private Cloud Cloud Database Deployment Infrastructure as a Service (IaaS) SQL Server on Microsoft Azure Virtual Machines Migrate existing SQL private cloud workload to cloud-hosted virtual machines Platform as a Service (PaaS) Take advantage of massive computational resources of Windows Azure SQL Database service Microsoft Azure SQL Database 9/19/2018

5 Pure relational structure Normalized and de-normalized data sets
OLTP Workloads Online databases: Pure relational structure Normalized and de-normalized data sets Relations, constrains, Multiple joins Real-time queries Key lookups Transactional behavior

6 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 Azure VM Virtualized Machines Database Services SQL Server Cloud Continuum Microsoft Azure SQL Database 9/19/2018

7 SQL Server on Microsoft Azure Platform Comparison
Microsoft Azure SQL Database (PaaS) SQL Server in Azure VMs (IaaS) Target organizations Startup-mode dev organizations Elasticity and flexibility, low friction Application compatibility Existing enterprise customers Traditional workloads Operations + Management Mostly auto-administered Reduced functionality (i.e.; reporting) Great single database Requires effort for multi-db Availability 99.9% availability Service Level Agreement (SLA) Requires development efforts if you need more (Almost) all the option of the box Requires infrastructural effort for full HA Performance + Scalability Shared Resources Requires scaling out Predictable performance May be limited by hw resources Migration effort from on premises Limited application compatibility (transactions) May require effort in case of scaling out Mostly transparent Can be more challenging to scale out if a single database is not enough Costs Optimized for low costs to buy and manage Licensing and VM costs could be not trivial SQL Server on Microsoft Azure Platform Comparison For SQL Server IaaS HADR focus on “SQL Server in WA VMs” 9/19/2018

8 SQL Server OLTP in Microsoft Azure VMs Scenarios
Dev/Test, big and small Lift & Shift Fastest time to solution - On-ramps to full PaaS Departments cutting the cord with central IT for B2B Inexpensive hosting alternative with pay per minute Cloud based learning/pre-sales demonstration Hybrid IaaS cross-premises databases Cloud Disaster Recovery (DR), on-demand cloud bursting Emerging scenarios taking advantage of pay per min price elasticity

9 Architecture: SQL Server in Microsoft Azure VMs
Microsoft Services 9/19/2018 1 2 3 Role Virtual Machine Implicit Cloud Service Implicit Cloud Service Availability Set Architecture: SQL Server in Microsoft Azure VMs Primary Secondary VM VM VM C:\ OS Disk D:\ Resource Disk Dynamic VHD E:\, F:\, etc. Data Disks No SLA SLA 99.95 Microsoft Azure Storage Blob RAM Cache Microsoft Azure Storage Blob (somewhere else) 1.) C:\ is for the OS or small databases. Any DB over 10GB in size should go on Data Disks. D:\ is for temporary storage only and is not persisted. No DB files of any kind including tempdb. 2.) No single instance SLA 3.) So what do we need to do to get the 99.5 SLA?  We need put our solution into a high availability solution and them put those machines into an availability set. You manage the availability of an application that uses multiple virtual machines by adding the virtual machines to an availability set. Availability sets are directly related to fault domains and update domains. A fault domain in Windows Azure is defined by avoiding single points of failure, like the network switch or power unit of a rack of servers. In fact, a fault domain is closely equivalent to a rack of physical servers. When multiple virtual machines are connected in a cloud service, an availability set places the virtual machines in different fault domains. Local Disk Cache Blobs 9/19/2018 Blob © 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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.

10 Extend on-prem apps to Microsoft Azure Virtual Machine
Windows Azure Virtual Network SQL Server in VM WINDOWS AZURE Extend SQL Server in VM Extend your datacenter Virtual Network makes it easy to extend your datacenter using Windows Azure much in the same way that you would set up and connect to a remote branch office. You retain control over the network topology and configuration, and manage it in the same way you would your on-premises infrastructure. Build distributed applications Virtual Network makes it easier to build cloud applications hosted in a hybrid environment, maintaining secure connections with on-premises infrastructure without the creation of custom codes. For example, a web application hosted in Windows Azure can securely access an on-premise SQL Server database server or authenticate users against an on-premise Active Directory service. ON-PREM Note : On-premises business application can access SQL Server instance deployed in Microsoft Azure VMs Connect SQL Server Business App

11 Move SQL Server and App to Microsoft Azure VM
Resource Management Dynamic Scaling High Availability and Durability Target Scenarios High Available Services Microsoft AZURE Periodic Workloads Business App Connect Unpredictable Growth SQL Server in VM Resource Management- When you deploy your application and services to the cloud, Windows Azure provides the necessary virtual machines, network bandwidth, and other infrastructure resources. If machines go down for hardware updates or due to unexpected failures, new virtual machines are automatically located for your application. The automatic infrastructure services provided by Windows Azure offer a low barrier of entry for application deployment and management. Dynamic Scaling-Dynamic scaling refers to the capability to both scale out and scale back your application depending on resource requirements. This is also referred to as elastic scale. If resource demands increase, new role instances running your application code can be provisioned to handle the load. When demand decreases, these instances can be removed so that you don't have to pay for unnecessary computing power. This scaling does not happen automatically, but it is easily achieved through either the web portal or the Service Management API. High Availability and Durability- Windows Azure provides a platform for highly available applications that can reliably store and access backend data through Windows Azure Storage services. First Windows Azure ensures high availability of your compute resources when you have multiple instances of each role. Role instances are automatically monitored, so it is able to respond quickly to hardware restarts or failures by automatically deploying a role to a new instance. Second, Windows Azure ensures high availability and durability for data stored through one of the storage services. Windows Azure Storage services replicate all data to at least three different servers. Target Scenarios High Available Services- Windows Azure is well-suited to hosting highly available services. This is accomplished by the service monitoring and automatic instance management performed in the Windows Azure data center. Periodic Workloads -Another good fit for Windows Azure is some form of an "on and off" workload. Some applications do not need to run continuously. Windows Azure allows you to easily create, deploy, and share this type of application. But once its purpose is accomplished, you can remove the application and you are only charged for the time it was deployed. You should use code or scripting to automatically deploy the application at the appropriate time, and shutdown the application when it is no longer needed. Unpredictable Growth -All businesses have a goal of rapid and sustainable growth. But growth is very hard to handle in the traditional on-premises model. If the expected growth does not materialize, you've spent money maintaining underutilized hardware and infrastructure. But if growth happens more quickly than expected, you might be unable to handle the load, resulting in lost business and poor customer experience. For small companies, there might not even be enough initial capital to prepare for or keep up with rapid growth Workload Spike -This is another workload pattern that requires elastic scale. Consider an example of a sports news web site and supporting SQL databases. Even as their business is steadily growing, there is still the possibility of temporary spikes or bursts of activity. For example, if they are referenced by another popular news outlet, the numbers of visitors to their site could dramatically increase in a single day. In a more predictable scenario, major sporting events and sports championships will result in more activity on their site Infrastructure Offloading – Many of the most common cloud scenarios take advantage of the elastic scale of Windows Azure. However, even applications with steady workload patterns can realize cost savings in Windows Azure. It is expensive to manage your own data center, especially when you consider the cost of energy, people-skills, hardware, software licensing, and facilities. It is also hard to understand how costs are tied to individual applications. In Windows Azure, the goal is to reduce total costs as well as to make those costs more transparent. Workload Spikes Flexibility & Control Low TCO for Existing Apps Managed Infrastructure Full SQL Server Capability Infrastructure Offloading Note : Business application and SQL Server instance are deployed in Windows Azure VMs

12 Move Existing Tier 2 & 3 Apps and Database
Microsoft Services 9/19/2018 Flexibility & Control Low TCO for Existing Apps Full SQL Server Capability Managed Infrastructure Move Existing Tier 2 & 3 Apps and Database Option 1 Option 2 VHD Virtual Machine Database In moving your existing applications, we recommend starting with your departmental Tier 2 and Tier 3 applications.  If the application is not yet virtualized, you can use System Center 2012 to virtualize the applications to Windows Server Hyper-V .VHD format, alternatively if your application is already virtualized on another virtualization technology you can use System Center 2012 to convert the already virtualized application to Windows Server Hyper-V .VHD format.  Either way System Center 2012 makes this process very easy for you.  Once the application is in the proper format you can either transfer just the database to the Windows Azure Virtual Machine or alternatively move the entire on-premises VHD to the Windows Azure VM.  Depending upon the size of the SQL Database, you also may need to place the data on a separate virtual disk and separately attach to the OS/Application VHD. P2V Windows Server Hyper-V VHD V2V Non-Virtualized Virtualized 9/19/2018 © 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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.

13 Deploy SQL Server OLTP in Microsoft Azure VMs
Microsoft Services 9/19/2018 Deploy SQL Server OLTP in Microsoft Azure VMs Use the Gallery image Currently: SQL 2008 R2 Service Pack 2 (SP2), SQL 2012 Service Pack 1 (SP1), SQL 2014 on different Windows Server OS Default options Includes SSIS, RS, AS License: Multiple SKUs + Pay by Minute Image refresh monthly (roughly) Once deployed you patch it Bring your own image Upload VHD to WA storage account, use image to instantiate VM Use Sysprep to create template SQL Server 2008 R2 and up License Mobility with Software Assurance You create image and patch it 9/19/2018 © 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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.

14 Develop & Test New Database Apps
Microsoft Services 9/19/2018 Flexibility & Control Low TCO for Existing Apps Full SQL Server Capability Managed Infrastructure Develop & Test New Database Apps dEPLOY Test Microsoft Azure Virtual Machines For development and test in a Windows Azure VM you start by creating a base virtual machine for SQL, and then you can use the same on-premise SQL Server Data Tools that you are familiar to develop your on- premise applications. In fact you can run your development tools on-premises and attach to your SQL development database in Windows Azure. You then can deploy the VM to start testing the application in Azure VM’s, and you can later decide to deploy the application back on premise without having to modify the application. Develop SQL Server Data Tools On-Prem Deploy 9/19/2018 © 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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.

15 Develop & test new apps Data & Application Tier
PROVISION DEVELOP DEPLOY MANAGE Provision new Microsoft Azure VM based on SQL Server template using Windows Azure Portal: Develop new applications using SQL Server Data Tools and Visual Studio Configure access using Microsoft Azure Portal and Windows Firewall in the VM Monitor application over time using Microsoft Azure Portal and SQL Server Management Studio Create deployment scripts using SQL Server Data Tools and Visual Studio Deploy and test package to Windows Azure VM using SQL Server Data Tools and Visual Studio

16 Microsoft Azure VM Sizes
Microsoft Services 9/19/2018 Microsoft Azure VM Sizes Virtual Machine Size CPU Cores Memory Disk Space for Virtual Machines Allocated Bandwidth (Mbps) Maximum data disks (1 TB each) Maximum IOPS (500 maximum per disk) ExtraSmall Shared 768 MB 20 GB 5 1 1x500 Small 1.75 GB 70 GB 100 2 2x500 Medium 3.5 GB 135 GB 200 4 4x500 Large 7 GB 285 GB 400 8 8x500 ExtraLarge 14 GB 605 GB 800 16 16x500 A6 28 GB 1,000 A7 56 GB 2,000 These values may change, check the source for latest updates. Source: © 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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.

17 Smaller DBs (<10GB) on C:\, anything bigger on data disks
Don’t use D:\ even for TempDB For IO intensive workloads, leave default cache settings (disabled) for data disks Stripe Data disks using SQL file groups for higher IOPS/large files, but be wary of geo-replication effects Don’t use multiple storage accounts within a single VM Use Data compression, Instant file initialization Have a plan for variability in performance Recommend practices Whitepaper

18 <Partner> Services Primary Objectives
Identify and assess the OLTP workloads within <customer> environment Provide a comprehensive migration report for those workloads Provide migration plan for these workloads and guidance on deploying SQL Server infrastructure for migration on Windows Azure Virtual Machines 9/19/2018

19 Offering Activities and Timeline
2 Weeks before start Week 1 Weeks 2-3 Week 4 PRE-ENGAGEMENT ENVISION PLAN BUILD Offering Activities and Timeline Environment Assessment Questionnaire Project Kickoff Perform Workload Inventory Create SQL Server Environment in Windows Azure VMs Roles and Responsibilities Categorize and Analyze Migrate SQL Server OLTP Workload Vision and Scope Compile Inventory Reports Project Closeout Project Plan Final Migration Report Conditions of Satisfaction Tactical Migration Plan 9/19/2018


Download ppt "Microsoft Services 9/19/2018 SQL OLTP on Microsoft Azure Virtual Machines (IaaS) Jumpstart Delivery Training Date of Presentation © 2010 Microsoft Corporation."

Similar presentations


Ads by Google