1. Cloud OS Data Platform
Data Platform in Microsoft Azure

2. Public Cloud SQL Server in a Microsoft Azure Virtual Machine
Move your existing database applications to the cloud using Microsoft Azure Virtual Machines (VMs).
Move Existing SQL Server Database
Backup & Restore Database to the Cloud
Update Application Connection string to point to SQL Server Database on Microsoft Azure VM
KEY SCENARIO
Use SQL Server in Microsoft Azure VM.

3. Public Cloud SQL Server in a Microsoft Azure Virtual Machine
KEY Benefits
Full SQL Server Capabilities
Managed Infrastructure for SQL Server
Low TCO for Existing Apps
Flexibility & Control
Use Existing License

4. Key Benefits Microsoft Azure SQL Database No App Changes Required
Low TCO for Existing Apps
No App Changes Required
Familiar Development tools
Library of VM Templates
Full SQL Server Capability
High Availability of Database with AlwaysOn Availability Groups
Advanced Security (Transparent data encryption & auditing)
Full Business Intelligence Functionality
Flexibility & Control
Full Control of Virtual Machine
Common Identity (Active Directory Integration)
Managed Infrastructure
Fully Managed Infrastructure for SQL Server
99.9% Service Level Agreement (SLA) for Virtual Machine
Single Pane of Glass to Manage with System Center 2012

5. Backup & Restore to Cloud
Flexibility & Control
Low TCO for Existing Apps
Full SQL Server Capability
Managed Infrastructure
Restore in Azure Virtual Machine
Microsoft Azure
Direct URL Backup
To Azure BLOB Storage
SQL Server Management Studio
SQL Server in VM
On-Prem SQL Server
Note : SQL Server 2005,2008/2008 R2 backup is done on file system and copied to Azure blob storage. Then the backup is restored within SQL Server instance on Microsoft Azure VM

6. Backup database to the cloud DATA TIER-Database backup
PROVISION
DEVELOP
DEPLOY
MANAGE
Identify databases for backup using SQL Server Management Studio
Create Blob container to store backup files using Microsoft Azure Portal
Write database backup files to Microsoft Azure using SQL Server Management Studio
Routine backup maintenance tasks using SQL Server Management Studio
Provision Microsoft Azure Storage Accounts using Microsoft Azure Portal
Create SQL Server credential for backup in SQL Server Management Studio

7. Move existing SQL Server apps DATA TIER : Restore the DATABASE
PROVISION
DEVELOP
DEPLOY
MANAGE
Identify database(s) to move using MAP toolkit:
Create database deployment package using SQL Server Management 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
Provision updated Microsoft Azure VM based on SQL Server template using Microsoft Azure Portal:
Deploy database package to Microsoft Azure VM using SQL Server Management Studio

8. Extend on-prem apps to Microsoft Azure Virtual Machine
SQL Server in VM
Microsoft Azure
SQL Server in VM
Extend
Microsoft Azure Virtual Network
ON-PREM
Note : On-premises business application can access SQL Server instance deployed in Microsoft Azure VMs
Connect
Business App
SQL Server

9. 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, Microsoft 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.
Because you only pay for what you use, you can start off with a smaller investment rather than incurring the typical upfront costs required for an on-premises deployment. This can be especially useful for small companies. In an on-premises scenario, these organizations might not have the data center space, IT skills, or hardware skills necessary to successfully deploy their applications. The automatic infrastructure services provided by Microsoft 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. Before describing how this works, you should understand the basic architecture of a Microsoft Azure application. In Microsoft Azure, you create roles that work together to implement your application logic. For example, one web role could host the ASP.NET front-end of your application, and one or more worker roles could perform necessary background tasks. Each role is hosted on one or more virtual machines, called role instances, in the Microsoft Azure data center. Requests are load balanced across these instances. For more information about roles, see the paper The Microsoft Azure Programming Model.
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 is much different from an on-premises deployment where hardware must be over-provisioned to anticipate peak demands. This scaling does not happen automatically, but it is easily achieved through either the web portal or the Service Management API. The paper Dynamically Scaling an Application demonstrates one way to automatically scale Microsoft Azure applications. There is also an Autoscaling Application Block created by the Microsoft Patterns and Practices team.
High Availability and Durability- Microsoft Azure provides a platform for highly available applications that can reliably store and access backend data through storage services or Microsoft Azure SQL Database.
First Microsoft 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, Microsoft Azure ensures high availability and durability for data stored through one of the storage services. Microsoft Azure storage services replicate all data to at least three different servers. Similarly, SQL Database replicates all data to guarantee availability and durability.
Other Microsoft Azure services provide similar high availability guarantees. For more information, see the Microsoft Azure SLA.
High Available Services- Microsoft Azure is well-suited to hosting highly available services. Consider an online store deployed in Microsoft Azure. Because an online store is a revenue generator, it is critical that it stay running. This is accomplished by the service monitoring and automatic instance management performed in the Microsoft Azure data center. The online store must also stay responsive to customer demand. This is accomplished by the elastic scaling ability of Microsoft Azure. During peak shopping times, new instances can come online to handle the increased usage. In addition, the online store must not lose orders or fail to completely process placed orders. Microsoft Azure storage and SQL Database both provide highly available and durable storage options to hold the order details and state throughout the order lifecycle.
Periodic Workloads-Another good fit for Microsoft Azure is some form of an "on and off" workload. Some applications do not need to run continuously. One simple example of this is a demo or utility application that you want to make available only for several days or weeks. Microsoft Azure allows you to easily create, deploy, and share that application with the world. But once its purpose is accomplished, you can remove the application and you are only charged for the time it was deployed.
Also consider a large company that runs complex data analysis of sales numbers at the end of each month. Although processing-intensive, the total time required to complete the analysis is at most two days. In an on-premises scenario, the servers required for this work would be underutilized for the majority of the month. In Microsoft Azure, the business would only pay for the time that the analysis application is running in the cloud. And assuming the architecture of the application is designed for parallel processing, the scale out features of Microsoft Azure could enable the company to create large numbers of worker role instances to complete more complex work in less time. In this example, you should use code or scripting to automatically deploy the application at the appropriate time each month.
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 the previous example of a sports news web site. 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-As demonstrated in the previous examples, many of the most common cloud scenarios take advantage of the elastic scale of Microsoft Azure. However, even applications with steady workload patterns can realize cost savings in Microsoft 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 Microsoft Azure, the goal is to reduce total costs as well as to make those costs more transparent. The paper, Cloud Optimization – Expanding Capabilities, while Aligning Computing and Business Needs, does a great job of explaining typical on-premises hosting costs and how these can be reduced with Microsoft Azure. Microsoft Azure also provides a pricing calculator for understanding specific costs and a TCO (Total Cost of Ownership) calculator for estimating the overall cost reduction that could occur by adopting Microsoft Azure. For links to these calculator tools and other pricing information, see the Microsoft Azure web site.
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 Microsoft Azure VMs

10. Extend on-prem apps to Microsoft Azure virtual machine
PROVISION
DEVELOP
DEPLOY
MANAGE
Provision VPN between on-premise and Microsoft Azure using Microsoft Azure Virtual Network
Partition database and modify applications to point to SQL Server in Microsoft Azure VM 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
Provision new Microsoft Azure VM based on SQL Server template using Microsoft Azure Portal:
Deploy database package to Microsoft Azure VM using SQL Server Management Studio
Create database deployment package using SQL Server Management Studio
Step 1: You can provision a VPN connection between on-prem and Microsoft Azure using Microsoft Azure Virtual Network. Then you need to provision a new virtual machine using one of the stock SQL Server images using Microsoft Azure portal.
Step 2: You can then use SQL Server Data Tools to modify applications to point to SQL Server in Microsoft Azure Virtual Machine. Then you can create a database deployment package using SQL Server Management Studio for the on-prem database(s) or use Database Export/Import Wizard to move the database(s) to SQL Server in Microsoft Azure Virtual Image.
Step 3: You need to configure security on both Microsoft Azure Portal endpoint as well as setting an inbound port in the virtual machine’s Windows Firewall. Then you can import the database(s) using the deployment package or using Database Export/Import Wizard.
Step 4: Once you have done that, you can monitor the virtual machine using Microsoft Azure Portal and monitor the SQL Server application using SQL Server Management Studio

11. © 2013 Microsoft Corporation. All rights reserved
© 2013 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

12. Public Cloud Database Purchasing Steps Select Supported SQL Server SKU
SQL Server in a Microsoft Azure Virtual Machine
Database Purchasing Steps
Select Supported SQL Server SKU
(2014, 2012, 2008 R2) (Enterprise, Standard, Web)
Select Virtual Machine Size
(price varies by size)
Now lets go through the steps you need to take to start utilizing the Microsoft Azure Virtual Machine and the Microsoft Azure SQL Database service.
Lets start with the VM:
First step is to determine the right version and edition of SQL Server you would like to use.
Next you select the appropriate virtual machine size. Again you can reference the sizing guidance we provided earlier to determine the which is VM size is appropriate for your application needs.
Finally you can either migrate your existing SQL Server license if you have Software Assurance on your SQL Server licenses or alternatively you can sign up and pay hourly use rates for the SQL server license.
On the SQL Database service side:
- You simply select the SQL Database size from the Microsoft Azure customer portal and pricing varies by size and they you can select to pay as you go or buy a discounted 6 month per-paid usage plan
Migrate Existing License with SA or
Sign Up and Pay Hourly