Azure SQL: What to use when and how to migrate

Azure SQL: What to use when and how to migrate
Anna Hoffman (Thomas) Azure SQL: What to use when and how to migrate

12/17/2019 7:25 PM SQL Server on the Microsoft Azure Platform SQL Server Ground to Cloud Workshop Anna Hoffman (Thomas) Azure SQL Engineering, Microsoft © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Sponsors You Rock! Gold Silver Bronze Many thanks to our sponsors, without whom such an event would not be possible.

Thank you For the Venue

Agenda Azure SQL Migrating to Azure SQL
Scenario – Tailspin Toys Gaming Demos! I will show you a lot, but I will give you access to full courses at the end so you can do on your own!

Azure SQL

Azure SQL SQL virtual machines Managed instances Databases
12/17/2019 7:25 PM Azure SQL SQL virtual machines Managed instances Databases Best for migrations and applications requiring OS-level access Best for most lift-and-shift migrations to the cloud Best for modern cloud applications. Hyperscale and serverless options are available © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Azure SQL virtual machines
The contract on my hardware is expiring We have instances of SQL Server 2008 and 2008 R2 We want to migrate to the cloud as fast as possible We use third party software that needs OS-level access We want to extend our on- premises apps to Azure We need an unlimited number of DBs Challenges Solution: Azure SQL virtual machines Best for migrations and applications requiring OS-level access SQL Server and OS server access Expansive SQL and OS version support Automated manageability features for SQL Server Automatic security patching Point in time restore with Azure Backup Free Extended Security Updates for SQL Server 2008/R2* Save 5x compared to AWS EC2** 435 percent overall return on an Azure IaaS investment over five years (Forrester Consulting) * ESU worth 75% of license every year for the next three years after EOS; ** Applicable to Azure Marketplace images, customers using customer SQL Server 2008/R2 custom images can download the ESU for free and manually apply. VMs: Allscripts professional-services-azure Move 600 VMs to Azure within a few weeks. Some time later moving some to MI Rehost SQL Server 2008 and 2008 R2 in Azure Virtual Machines to get three years of Extended Security Updates at no additional charge and upgrade to a newer version when ready 435 percent overall return on an Azure IaaS investment over five years (for a composite organization based on the interviewed customers) (Forrester Consulting) iaas Customer example

What is Resource Provider?
SQL Server on Azure VM What is Resource Provider? Resource Provider brings the functionality of Azure Marketplace images to SQL Server instances self-installed on Azure Virtual Machines Key customer benefits Comprehensive feature set Dashboard view for VM awareness Simple license conversions Straightforward compliance There are four customer benefits to registering a self-installation of SQL Server on Azure Virtual Machines with a Resource Provider: 1.) Comprehensive feature set – get access to benefits like auto-patching and auto-backup that previously were only available in PAYG and BYOL Azure Marketplace images 2.) Dashboard view – manage all SQL VM and SQL DB instances in the new “Azure SQL” blade of the Azure Portal 3.) Simple license conversations – convert self-installations to PAYG images for cost flexibility 4.) Straightforward compliance – automatically comply with the requirement to let Microsoft know when you are using Azure Hybrid Benefit To learn more, go to aka.ms/sqlvm_rp (blog post) and aka.ms/sqlvm_rp_documentation (documentation)

Key benefits of Resource Provider (RP) on self-installations
SQL Server on Azure VM Key benefits of Resource Provider (RP) on self-installations Comprehensive feature set Dashboard view for VM awareness Simple license conversions Straightforward compliance Self-installed VMs registered with RP now can access automation features in Azure Marketplace images Leverage auto-backup and auto-patching to avoid time-consuming admin and VM customization Azure VMs are now discoverable on the new Azure SQL blade in Azure Marketplace Easily manage your SQL VM and SQL PaaS deployments from one central location Self-installed VMs with RP can be easily converted to PAYG images Save money by converting variable workloads with Software Assurance to PAYG images Self-installed VMs with RP automatically indicate usage of Azure Hybrid Benefit Ensure compliance with Azure terms and conditions without any extra effort There are four customer benefits to registering a self-installation of SQL Server on Azure Virtual Machines with a Resource Provider: 1.) Comprehensive feature set – get access to benefits like auto-patching and auto-backup that previously were only available in PAYG and BYOL Azure Marketplace images 2.) Dashboard view – manage all SQL VM and SQL DB instances in the new “Azure SQL” blade of the Azure Portal 3.) Simple license conversations – convert self-installations to PAYG images for cost flexibility 4.) Straightforward compliance – automatically comply with the requirement to let Microsoft know when you are using Azure Hybrid Benefit To learn more, go to aka.ms/sqlvm_rp (blog post) and aka.ms/sqlvm_rp_documentation (documentation) Learn more aka.ms/sqlvm_rp and aka.ms/sqlvm_rp_documentation

Azure SQL Managed instance
We want to migrate to Azure PaaS We want to remove some of the management overhead and stress with regards to business continuity, high availability, and disaster recovery We need instance-scoped features like SQL Server Agent, Database Mail, Service Broker, CLR, etc. Challenges Solution: Azure SQL Managed instance Best for most lift-and-shift migrations to the cloud Single instance or Instance pool SQL Server surface area (vast majority) Native virtual network support Fully managed service SLA with an availability guarantee up to % Projected return on investment of 212 percent over three years (Forrester Consulting), along with: A 20 percent increase in IT productivity. A 40 percent productivity improvement for database administrators. Managed Instance: Komatsu us/story/komatsu-australia-manufacturing-azure Moved about 1.5 TBs of data very smoothly because of the near 100% compatibility with SQL Server 49% reduction in cost and 25% increase in performance gains Customer example

Azure SQL Database Challenges Solution: Customer example
I want to build new apps quickly I don’t want to worry about managing SQL Server at an instance or OS level I have (or will have) very large databases in the future I have unpredictable workload needs I want to integrate Azure services into my applications Challenges Solution: Azure SQL Database Best for modern cloud applications. Hyperscale and serverless options are available Single database or elastic pool Hyperscale storage (up to 100TB) Serverless compute Fully managed service Private link (preview) SLA with an availability guarantee up to % Price-performance leader for mission-critical workloads while costing up to 86 percent less than AWS RDS (GigaOm) Potential demos here: Online gaming site build demo for BC MI and read scale out Serverless wine quality database Database: AccuWeather us/story/accuweather-partner-professional-services-azure New intelligent applications. Using Azure Machine Learning Services to make sales and customers predictions Customer example

SQL Database versus Managed Instance
In SQL MI you control the instance. In SQL DB you do not. As a result a number of features are available in MI that are not in DB: E.g. SQL Server Agent, Linked Servers, Cross database transactions, Common Language Runtime, Resource governor, SQL Server Auditing, Time zone choice, Service Broker, Collation on server / instance level Because you control the instance, a number of features are not in MI that are in DB: E.g. Auto-scale (serverless), Automatic tuning, Availability Zones, Azure Resource Health, SQL Data Sync, R Services (in preview) For a detailed comparison see database/sql-database-features Only a detailed analysis of requirements can tell you which is the best fit: 𝑆𝑄𝐿𝐷𝐵𝑀𝐼 ≠𝑆𝑄𝐿𝐷𝐵++

SQL Server 2019 comparison to Azure SQL
Feature SQL Server 2019 Azure SQL Intelligent Query Processing Lightweight Query Profiling In-Memory Database Always Encrypted with Enclaves Data Classification Accelerated Database Recovery UTF-8 Extensibility Framework * PolyBase Data Virtualization * * In-Memory OLTP exists in both SQL Server and Azure

Challenges with managing Very Large Databases (VLDB)
Size of data Scaling Compute Operations take a LONG time (days in some cases) Ongoing operations degrade database performance Can cause outages and downtime Provisioning more storage to expand the database can be painful Logistics of moving to larger box Economics of sizing for max peaks Overview: There are challenges with very large databases whether on –premise or in the cloud. From size of data to scaling compute. Talking Points: Anything that requires size-of-data operations is a big problem Operations take a LONG time (days in some cases) Ongoing operations degrade database performance Can cause outages and downtime Provisioning more storage to expand the database can be painful Scaling compute power can be challenging Logistics of moving to larger box Economics of sizing for max peaks

What is Azure SQL Database Hyperscale?
Cloud native Architected for cloud SQL Seamless compatibility Fully compatible with Azure SQL Database Storage Scalable new storage architecture Performance VLDB operations without VLDB headaches No limits Scale compute and storage Large database Support for 100TB+

Hyperscale and Azure SQL DW
HS SMP Hyperscale Real-time analytics/HTAP SQL Server, Oracle… MPP Azure DW Big Data Analysis APS, Teradata…

Challenges with sporadic or unpredictable usage
Line of business apps Expense reporting and employee tracking apps Procurement systems E-commerce Opening new marketplaces, marketing campaigns, sales promotions Content management systems Updating and publishing web content Content clearinghouses that pull select content by third parties Dev/test workloads Handling unpredictable workload needs Line-of-business applications, dev/test databases, content management and e-commerce systems are just some examples across a range of applications that often fit the usage pattern ideal for serverless. Serverless is also well-suited for new applications with compute sizing uncertainty or workloads requiring frequent rescaling in order to reduce costs.

Optimize price to performance with per-second billing
8:00 9:00 10:00 11:00 12:00 13:00 14:00 15:00 16:00 17:00 18:00 19:00 20:00 21:00 22:00 23:00 0:00 1:00 2:00 3:00 4:00 5:00 6:00 7:00 Min vcores Number vCores 4 CPU usage 1 Inactive Paused Max vcores Vcores used Vcores billed Compute resources scale dynamically up or down based on workload requirements Configure minimum and maximum vCores to define the range of available compute capacity Use auto-pause delay to define the time period the dataset must be inactive before pausing Pay for compute based on the vCores and memory used per second, with lowest billing based on configured vCore minimum Serverless automatically scales compute for single databases based on workload demand and bills for compute used per second. In serverless, compute scaling within configurable limits is managed by the service to continuously right-size resources. Serverless also provides an option to automatically pause the database during inactive usage periods and automatically resume when activity returns. During periods of inactivity, you only pay for storage.

When is elastic pools the right choice?
Multiple databases with unpredictable and intermittent usage patterns can be consolidated into a single server and use elastic pools for better price optimization Elastic pools Customer example In the case of multiple databases with unpredictable and intermittent usage - which is not uncommon in multi-tenant SaaS scenarios – consolidating the databases into a single server, then using elastic pools will likely provide better price optimization Objective: Scaling out refers to building apps using multiple databases spread over multiple independent nodes. Typically nodes are cost-effective, commodity class hardware. There are multiple approaches to scale-out but among alternatives, patterns such as sharding and horizontal partitioning provide the best scalability. With these patterns, apps can decentralize their processing, spread their workload to many nodes, and harness the collective computational capacity. You can achieve linear cost-to-scalability ratio as you add more nodes. Talking Points: Achieving elasticity and scale for cloud applications has been straightforward for compute and blob storage―simply add or subtract units. But it has remained a challenge for stateful data processing in relational databases. We have seen these challenges emerge most prominently in the following two scenarios: Growing and shrinking capacity for the relational database part of your workload Managing hotspots that may arise affecting a specific subset of data―such as a particularly busy end customer (tenant) Traditionally, scenarios like these have been addressed by investing in larger-scale database servers to support the application. However, this option is limited in the cloud, where all processing happens on predefined commodity hardware. Instead, distributing data and processing across many identically structured databases (a scale-out pattern known as "sharding") provides an alternative to traditional scale-up approaches both in terms of cost and elasticity. n. Elastic Pools: Paychex azure-sql-database-us 650,000 businesses across the U.S. - able to manage time and pay management for all of them in business-critical applications

Azure SQL SQL virtual machines Managed instances Databases
12/17/2019 7:25 PM Azure SQL SQL virtual machines Best for migrations and applications requiring OS- level access Managed instances Databases Best for most lift-and-shift migrations to the cloud Best for modern cloud applications. Hyperscale and serverless options are available SQL Server and OS server access Expansive SQL And OS version support Automated manageability features for SQL Server SQL virtual machine Single instance SQL Server surface area (vast majority) Native virtual network support Fully managed service Resource sharing between multiple instances to price optimize Fully managed service Managed instances as small as 2 vCore Instance pool Hyperscale storage (up to 100TB) Serverless compute Fully managed service Single database Resource sharing between multiple databases to price optimize Simplified performance management for multiple databases Fully managed service Elastic pool © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Flexible compute, storage & performance options
Simplicity We remain committed to the DTU- based model and the simplicity it offers customers who want a pre- configured solution Flexibility: The vCore-based model reflects our commitment to customer choice and to simplify the hybrid benefit for customers migrating from on- premises Customers pay for: Service tier + number of vCores Type and amount of data storage Number of IO Backup storage (RA-GRS) Service tier General purpose Business critical Hyperscale Best for Most budget-oriented workloads Critical business applications with high IO requirements. VLDB OLTP and HTAP workloads with highly scalable storage and read-scale requirements Deployment option Single / Elastic Pools Managed Instance Single Compute tiers Gen4: 1 to 24 vCore Gen5: 2 to 80 vCore Serverless: 0.5 to 16 vCore (preview) Gen4: 4 to 24 vCore Gen5: 4 to 80 vCore Storage Premium remote Local SSD Local SSD Cache 32GB – 8TB per instance 32GB – 4TB per instance Scale from 5GB to 100TB of storage in 1GB increments In-Memory Not supported Supported Read-write IO ~2ms for all data access <0.5ms for all data access <0.5ms for hot data access ~2ms otherwise Availability 2 read replicas 3 read replicas, zone-redundant HA 3 replicas, 1 read-scale replica, zone-redundant HA Primary read/write replica + up to 4 read replicas Backups RA-GRS, 7-35 days (7 days by default) LRS, ZRS, RA-GRS, 7-35 days (7 days by default) vCore model so we can get AHB: 1 Enterprise license core = 1 Business Critical core Business critical because online gaming wants the highest performance and HA Gen 5 so we can scale our compute more Also for read-scale replica, zone redundant HA Zone-redundant storage (ZRS) replicates your data synchronously across three storage clusters in a single region. Each storage cluster is physically separated from the others and is located in its own availability zone (AZ). Each availability zone—and the ZRS cluster within it—is autonomous and includes separate utilities and networking features. A write request to a ZRS storage account returns successfully only after the data is written to all replicas across the three clusters. When you store your data in a storage account using ZRS replication, you can continue to access and manage your data if an availability zone becomes unavailable. ZRS provides excellent performance and low latency. ZRS offers the same scalability targets as locally redundant storage (LRS). For latest information reference:

Migrating to Azure SQL

Data Migration Process
*Pre-migration*: - **Discover**: Inventory your source database assets and perform an application stack discovery. - **Assess**: Assess source workloads and fix recommendations. - **Convert**: Convert the source schema to work in the target environment. This is only relevant for heterogeneous migrations. *Migration*: - **Migrate schema, data, and objects**: Migrate the source schema and then migrate the source data to the target. - **Sync data**: Sync your target schema and data with the source. This is only relevant for minimal-downtime migrations. - **Cutover**: Cut over from the source to the target environment. This is only relevant for minimal-downtime migrations. *Post-migration*: - **Remediate applications**: Iteratively make any necessary changes to your applications. - **Perform Tests**: Iteratively run functional and performance tests. - **Optimize**: Based on the tests you performed, address any performance issues and then retest to confirm the performance improvements.

Upgrade & migration tools
12/17/2019 7:25 PM Upgrade & migration tools Azure Migrate + DMS + DMA NEW The Azure SQL data platform consists of three options: SQL Server on an Azure VM Azure SQL Database Managed Instance Azure SQL Database Each of the options will be discussed in more detail in the slides that follow. © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Azure Migration Program (AMP)
Available to all Azure customers, scaled through specialized migration partners Offers and incentives Best practice guidance Technical skill building Infrastructure and data foundations Migration planning and execution Azure trainers FastTrack for Azure engineers Specialized partners Digital resources Migration Tools The Azure Migration Program gives you prescriptive guidance for a step by step approach to cloud migration. AMP offers the opportunity to work closely with Microsoft experts and specialized migration partners to simplify and accelerate your migration. The program delivers: Technical skill building to ensure your organization can successfully adopt Azure Best practices for a step by step approach from start to finish Azure engineering support for data and infrastructure foundations Expert guidance from specialized migration partners Free Azure tools to help you efficiently execute migrations And cost effective offers to help you save money before, during, and after migration Reduce cost and risk | Accelerate migration velocity | Deliver customer success Learn more | Azure.com/AMP

Scenario

Tailspin Toys Gaming (online gameplay)
Primarily SQL Server 2008 R2 Founded in 2010, exponential growth since then Gaming services (VMs/databases) run on rented hardware Primarily software developers, few infrastructure and database resources Desire to build more intelligent applications with AI and Machine Learning What, when, and how can I migrate to the cloud? Want to leverage new security and performance features in Azure they’ve heard about Need Service Broker, do not want to rearchitect the solution to use an alternative Applications need better availability and less downtime

Pre-migration

Demo: Database Discovery and Assessment (Module 4.4)

Tailspin Toys – Recommended database
12/17/2019 7:25 PM Tailspin Toys – Recommended database Azure SQL Database Managed Instance Platform-as-a-Service (PaaS) Supports database migration from on-premises with minimal to no database changes (i.e. Service Broker) Provides the benefits of Azure SQL Database but adds capabilities that were previously only available in SQL VMs Includes a native virtual network (VNet) and near 100% compatibility with on-premises SQL Server Managed instance is a new deployment option of Azure SQL Database, providing near 100% compatibility with the latest SQL Server on-premises (Enterprise Edition) Database Engine. Provides a native virtual network (VNet) implementation that addresses common security concerns, and a business model favorable for on-premises SQL Server customers. The managed instance deployment model allows existing SQL Server customers to lift and shift their on-premises applications to the cloud with minimal application and database changes. At the same time, the managed instance deployment option preserves all PaaS capabilities (automatic patching and version updates, automated backups, high-availability ), that drastically reduces management overhead and TCO. Adds features that are not available in Azure SQL Database, such as cross-database queries, linked servers, CLR modules, and Service Broker. © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Flexible compute, storage & performance options
Simplicity We remain committed to the DTU- based model and the simplicity it offers customers who want a pre- configured solution Flexibility: The vCore-based model reflects our commitment to customer choice and to simplify the hybrid benefit for customers migrating from on- premises Customers pay for: Service tier + number of vCores Type and amount of data storage Number of IO Backup storage (RA-GRS) Service tier General purpose Business critical Hyperscale Best for Most budget-oriented workloads Critical business applications with high IO requirements. VLDB OLTP and HTAP workloads with highly scalable storage and read-scale requirements Deployment option Single / Elastic Pools Managed Instance Single Compute tiers Gen4: 1 to 24 vCore Gen5: 2 to 80 vCore Serverless: 0.5 to 16 vCore (preview) Gen4: 4 to 24 vCore Gen5: 4 to 80 vCore Storage Premium remote Local SSD Local SSD Cache 32GB – 8TB per instance 32GB – 4TB per instance Scale from 5GB to 100TB of storage in 1GB increments In-Memory Not supported Supported Read-write IO ~2ms for all data access <0.5ms for all data access <0.5ms for hot data access ~2ms otherwise Availability 2 read replicas 3 read replicas, zone-redundant HA 3 replicas, 1 read-scale replica, zone-redundant HA Primary read/write replica + up to 4 read replicas Backups RA-GRS, 7-35 days (7 days by default) LRS, ZRS, RA-GRS, 7-35 days (7 days by default) vCore model so we can get AHB: 1 Enterprise license core = 1 Business Critical core Business critical because online gaming wants the highest performance and HA Gen 5 so we can scale our compute more Also for read-scale replica, zone redundant HA Zone-redundant storage (ZRS) replicates your data synchronously across three storage clusters in a single region. Each storage cluster is physically separated from the others and is located in its own availability zone (AZ). Each availability zone—and the ZRS cluster within it—is autonomous and includes separate utilities and networking features. A write request to a ZRS storage account returns successfully only after the data is written to all replicas across the three clusters. When you store your data in a storage account using ZRS replication, you can continue to access and manage your data if an availability zone becomes unavailable. ZRS provides excellent performance and low latency. ZRS offers the same scalability targets as locally redundant storage (LRS). For latest information reference:

Read-only reporting Read Scale-out Read-only replica
12/17/2019 7:25 PM Read-only reporting Primary endpoint (read-write) Read-only endpoint Read Scale-out Read-only replica Free with SQL MI BC Also available in Hyperscale Always On AG SQL Super-fast SSD SQL Primary replica Secondary replica SQL SQL As part of the High Availability architecture, each database in the Premium, Business Critical or Hyperscale service tier is automatically provisioned with a primary replica and several secondary replicas. The secondary replicas are provisioned with the same compute size as the primary replica. The Read Scale-Out feature allows you to load-balance SQL Database read-only workloads using the capacity of one of the read-only replicas instead of sharing the read-write replica. This way the read-only workload will be isolated from the main read-write workload and will not affect its performance. The feature is intended for the applications that include logically separated read-only workloads, such as analytics. They could gain performance benefits using this additional capacity at no extra cost. 3 secondary replicas, 1 is read scale out with MI BC Secondary replica Secondary replica Business Critical service tier: collocated compute and storage © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Module 5: Migrating to Azure SQL
Switch PPT!

Migration

Demo: Migrate to Azure SQL Database Managed Instance (Module 5.1)

PoC – Gaming services Diagram of the preferred solution for the gaming services. The gaming services are hosted in a VNet, with subnets for MI, Game, Management, Auth, and a Gateway subnet. SQL MI instances are hosted in the MI subnet. Gaming IaaS VMs are hosted in the Game subnet. Authorization VMs are in the Auth subnet, and a JumpBox is in the Management subnet. On-premises resources can access the VNet through ExpressRoute or a VPN gateway.

Preferred migration solution
Azure Migrate Data Migration Assistant Azure Database Migration Service Azure Site Recovery Partner or Azure Migrate Program engagement Azure Hybrid Benefit Prepay for Reserved Capacity Cost minimization Azure Hybrid Benefit Reserved capacity payments DMS 3 month timeframe ASR AMP Partner engagement Dedicated resources

Azure Hybrid Benefit for SQL Server
S4, Solution Specialist Sales Summit 12/17/2019 7:25 PM Azure Hybrid Benefit for SQL Server License trade-in values Take an inventory of on-premises licenses to determine potential for conversion Convert on-premises cores to vCores to maximize value of investments 1 Standard license core = 1 General Purpose or Hyperscale core 1 Enterprise license core = 1 Business Critical core 1 Enterprise license core = 4 General Purpose or Hyperscale cores (virtualization benefit) SQL Server cores with SA license vCores on Azure SQL Database SQL Server Standard Edition General purpose or Hyperscale vCore Business critical vCore SQL Server Enterprise Edition customers can use an unlimited virtualization benefit for their on-premises workloads. However, moving to the cloud to take advantage of its management, flexibility and cost benefits can be cost prohibitive for some heavily virtualized customers. The Azure Hybrid Benefit for SQL Server provides SQL Enterprise Edition customers with Software Assurance the ability to get 4 cores in the cloud for every 1 core they own on-premises for workloads moving to the General Purpose or Hyperscale SKU – the SKU that best meets the requirements for highly virtualized workloads. This makes moving virtualized applications to SQL Database highly cost effective as customers will not have to purchase incremental vCores to move their virtualized application to the cloud. SQL Server Enterprise Edition 4x General purpose or Hyperscale vCores © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Post-Migration

Post-migration PoC Develop validation tests Set up test environment
Run validation tests Run performance tests Leverage tools like Database Experimentation Assistant and Query Tuning Assistant Explore and test Azure security, performance, and scale platform benefits Validate and optimize a migration – Scale a migration – Engage Azure Migrate Program or Partner *Pre-migration*: - **Discover**: Inventory your source database assets and perform an application stack discovery. - **Assess**: Assess source workloads and fix recommendations. - **Convert**: Convert the source schema to work in the target environment. This is only relevant for heterogeneous migrations. *Migration*: - **Migrate schema, data, and objects**: Migrate the source schema and then migrate the source data to the target. - **Sync data**: Sync your target schema and data with the source. This is only relevant for minimal-downtime migrations. - **Cutover**: Cut over from the source to the target environment. This is only relevant for minimal-downtime migrations. *Post-migration*: - **Remediate applications**: Iteratively make any necessary changes to your applications. - **Perform Tests**: Iteratively run functional and performance tests. - **Optimize**: Based on the tests you performed, address any performance issues and then retest to confirm the performance improvements.

Read-only reporting Read Scale-out Read-only replica
12/17/2019 7:25 PM Read-only reporting Primary endpoint (read-write) Read-only endpoint Read Scale-out Read-only replica Free with SQL MI BC Also available in Hyperscale Always On AG SQL SQL Super-fast SSD Primary replica Secondary replica SQL SQL As part of the High Availability architecture, each database in the Premium, Business Critical or Hyperscale service tier is automatically provisioned with a primary replica and several secondary replicas. The secondary replicas are provisioned with the same compute size as the primary replica. The Read Scale-Out feature allows you to load-balance SQL Database read-only workloads using the capacity of one of the read-only replicas instead of sharing the read-write replica. This way the read-only workload will be isolated from the main read-write workload and will not affect its performance. The feature is intended for the applications that include logically separated read-only workloads, such as analytics. They could gain performance benefits using this additional capacity at no extra cost. 3 secondary replicas, 1 is read scale out with MI BC Secondary replica Secondary replica Business Critical service tier: collocated compute and storage © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Demo: After the migration (Module 5.2)

How to go about securing Data
Prepare Environment Discover & Classify Data Assess Code & Configuration Protect data & lock down access Secure the application layer Monitor ongoing activities

Automatic discovery of columns with sensitive data
12/17/2019 7:25 PM SQL Data Classification Discover, classify, protect and track access to sensitive data Automatic discovery of columns with sensitive data Add persistent sensitive data labels Audit and detect access to the sensitive data Manage labels for your entire Azure tenant using Azure Security Center SQL Data Classification is a new feature in the Public Preview, that: Automatically discovers columns containing potentially sensitive data It provides a simple way to review and apply the classification recommendations through the Azure portal. The sensitive data labels are persisted in the database (metadata attributes) and it audits and detects access to the sensitive data. We offer built-in set of labels and information types, however customers can chose to define custom labels across Azure tenant using Azure Security Center Please note that we also offer data classification for SQL on-premises SQL using the latest SQL Server Management Studio. In the near future, we will allow managing policy for all your sensitive data ACROSS Azure integrated with MIP for holistic MS data classification story. © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Identify security misconfigurations Actionable remediation steps
12/17/2019 7:25 PM SQL Vulnerability Assessment Discover, track, and remediate security misconfigurations Identify security misconfigurations Actionable remediation steps Security baseline tuned to your environment Manual/periodic scans Coherent reports for auditors SQL Vulnerability Assessment provides a visibility into your database security state and allows constant improvements. In short, it runs a set of security checks that Identify security misconfigurations It allows setting a security baseline that customize VA results matching your environment. It provides a clear report which is very helpful for security audits. We also support SQL Vulnerability Assessment for SQL OnPrem using the latest SQL Server Management Studio. © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Detects potential SQL injection attacks
12/17/2019 7:25 PM Advanced Threat Protection Detect unusual and harmful attempts to breach your database. (2) Possible threat to access / breach data Attacker Detects potential SQL injection attacks Detects unusual access & data exfiltration activities Actionable alerts to investigate & remediate View alerts for your entire Azure tenant using Azure Security Center User Developer Apps Azure SQL Database To summarize what you have seen, SQL Threat Detection allows you to respond to unusual and harmful attempts to breach your database. 1) It is super simple to enable and requires no modifications to your application code. 2) It provides you with a set of world-class algorithms that learn, profile and detect potential SQL injections and unusual behavior patterns. 3) It triggers security alerts upon detection, which include clear description and actionable investigation and remediation steps. Audit Log Threat Detection (1) Turn on Threat Detection (3) Real-time actionable alerts © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Security Center - Security alerts examples
Database or Subscription scope

Demo: After the migration (Module 5.3)

What you will learn in this workshop
12/17/2019 7:25 PM Capability exists for Azure SQL Database (Managed instance, single databases, and elastic pools) What you will learn in this workshop Capability exists for Azure SQL VMs Azure Migrate Data Migration Assistant Discover and assess what and where to migrate to Azure Azure Database Migration Services Migrate to Azure SQL Managed Instance with little to no downtime SQL Data Discovery and Classification Vulnerability Assessment Improve database security with Advanced Data Security Online secondary read replica Obtain read-scale out for read only queries © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Next steps for Azure SQL + Migrations
12/17/2019 7:25 PM microsoft: Next steps for Azure SQL + Migrations Use our free training at The content from today is Modules 4 and 5 of SQL Ground to Cloud! Learn from videos and demos at See and reuse useful Azure SQL slides at Engage the Azure Migrate Program at © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Please evaluate on your way out!

Sponsors You Rock! Gold Silver Bronze Many thanks to our sponsors, without whom such an event would not be possible.

Hardware provided by: Evaluations Please rate this session!

PASS Deutschland e.V. For further information about future events, visit our PASS Deutschland e.V. booth in the exhibitor area.

Next steps for Azure SQL + Migrations
12/17/2019 7:25 PM microsoft: Next steps for Azure SQL + Migrations Use our free training at The content from today is Modules 4 and 5 of SQL Ground to Cloud! Learn from videos and demos at See and reuse useful Azure SQL slides at Engage the Azure Migrate Program at © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Section Title

Title Content

Title Only

Content Only

Title Content 1 Content 2

Azure SQL: What to use when and how to migrate

Similar presentations

Presentation on theme: "Azure SQL: What to use when and how to migrate"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Azure SQL: What to use when and how to migrate

Similar presentations

Presentation on theme: "Azure SQL: What to use when and how to migrate"— Presentation transcript:

Similar presentations

About project

Feedback