Updating From SQL Server 2008 to Microsoft Azure

Microsoft’s SQL Server 2008 will reach end of support this July. Get a demonstration on how to migrate from this legacy application to Azure. Avoid business disruptions, security risks, and compliance issues by preparing to update your systems now.

1.Azure and SQL Modernization Name | Title

2.Agenda • Migration Drivers • Overview of SQL Server options in Azure • Hands on Workshop

3. Software and Security threats hardware refresh Urgent capacity Compliance needs Quickly Application innovation integrate acquisitions Software end Datacenter Migration of support contracts expiry drivers

4.SQL 2008 End of Life Impact End of support means: End of Life timetable: No security updates SQL Server 2008 and 2008 Compliance concerns R2 Windows Server 2008 and 2008 Missed innovation opportunities R2 2018 2019 2020

5.End of Support – What are the Options? Focus of Discussion and Lab Lift-and-shift to PaaS SQL DB MI is compatible with versions as far back SQL with Azure SQL as SQL Server 2005; no more future upgrades or Database Managed patches required as SQL DB will always run on the Instance (MI) latest feature as part of fully managed services Modernize to Azure Upgrade to SQL Server 2017 on Azure VMs, or SQL Server 2008/R2 Move to IaaS with Move “as-is” with SQL Server and Windows end of support Azure SQL VM Server 2008/R2 and get 3 years of Extended Security Updates included Modernize on premises Upgrade to SQL Server 2017+ (and Upgrade on premises Windows Server 2016) or stays “as-is” at 2008 and purchase Extended Security Updates

6.4 cloud path migration approaches Rehost Refactor Rearchitect Rebuild (lift and shift) Migrate applications as-is Take advantage of Modernize your app into a Rebuild an application for the benefits of the infrastructure as a service resilient, highly scalable, from scratch using cloud- cloud without the risks or (IaaS) and platform as a independently deployable native technologies costs of making code service (PaaS) with no architecture changes wholesale code changes

7.Defining these things… On Premises Infrastructure Platform Software (as a Service) (as a Service) (as a Service) You manage Applications Applications Applications Applications You manage Data Data Data Data Runtime Runtime Runtime Runtime Managed by vendor Middleware Middleware Middleware Middleware You manage Managed by vendor O/S O/S O/S O/S Managed by vendor Virtualization Virtualization Virtualization Virtualization Servers Servers Servers Servers Storage Storage Storage Storage Networking Networking Networking Networking

8.Defining these things… On-Prem IaaS PaaS SaaS Data classification and accountability Client & end-point protection Identity & access management Application level controls Network controls Host Infrastructure Physical Security Provider management of risk Customer management of risk Shared Responsibility Physical | Networking Data Classification and data accountability

9.Azure SQL Options

10. SQL Options VMs Singleton Elastic Pool Managed Instance Fully configurable One database per app pattern New multi-tenant SaaS apps or Lift-and-shift rich SQL apps to modernized existing apps to PaaS Choice of OS, SQL Primarily an OLTP store, no SaaS Version, features instance level features Best blend of HADR features, High flexibility while maintaining high Full control Highly scalable, built in HADR compatibility

11. Azure SQL Database – Single Database SQL Database • Primary and Initial SQL offering in Azure (PaaS) • Scoped as single logical database • Provision and scale dynamically Singleton • Two purchasing options: • Database Transaction Unit (DTU) • vCore licensing

12. Scale to meet demand • Scale individual databases up/down via portal, PS, APIs, or T-SQL to reflect actual or anticipated demand 4 TB • Database remains online while scaling P15 • In Memory OLTP on Premium P11 • Hourly billing provides cost efficiency P6 1 TB 250 GB P4 P2 P1 S3 S2 S1 B S0 5 10 20 50 100 125 250 500 1000 1750 4000

13.Azure SQL Database: HA / Replicas Single Logical • Majority quorum up to 4 replicas Database • Transparent automatic failover • Uptime SLA of 99.99% T-SQL Query DB • Zero user or admin config Read Ack Write P Ack Ack P S P S S S Write Write S S Reads are completed at the primary Writes are replicated to secondaries

14.(Preview) Azure SQL Database Hyperscale 100 TB Reliable and available Scalable High performance

15. Database Advisor improves performance Index tuning recommendations tailored to each DB Intelligent service for implementing and validating index recommendations

16. Active geo-replication Self-service activation in Premium/Standard/Basic Create up to 4 readable secondaries Replicate to any Azure region Geo-replicated database Automatic transactional data replication, asynchronous REST API, PowerShell or Azure Portal

17. Azure SQL Database Elastic Pools • Pools resources (DTU/vCore) into logical groups SQL Database (PaaS) • Allows databases within the pools to share allocation • Ideally suited for large collections of Elastic Singleton Pool databases with some workload variance.

18. Most common blockers: Azure SQL DB • No .NET CLR frequent roadblocks • No SQL Agent, no SSIS/SSRS • No cross database connectivity • No low level access, filestream/filetable Fully documented: https://aka.ms/azuresqlcomparison

19. Azure SQL Database Managed Instance SQL Database A flavor of SQL DB designed to enable (PaaS) easy migration to fully managed PaaS, for almost any application! Managed Elastic Singleton Instance Pool Full isolation and New business Easy lift and shift Fully managed PaaS security model • Fully-fledged SQL • Built on the same • Native VNET • Competitive instance with nearly PaaS service implementation • Transparent 100% compat with infrastructure • Private IP addresses • Frictionless on-prem • All PaaS features

20.Easy migration: nearly 100% like SQL Server Security • TDE • Row level security • SQL Audit • Always Encrypted

21.The Workshop

22.Tools and services for your migration journey

23. Online migration with backup and restore technology SQL Server to Azure SQL Database Managed Instance example 1.1 Provide existing backups in network share Virtual Network (VNET) Subnet used for MI 2.2 DMS upload backup files to Azure storage 3.3 DMS initiate the migration to Azure SQL MI Cloud network Azure Blob Storage 4 4. Full backup restored and Transaction log backups 4 2 continuously applied until cutover SQL DB Managed Instance Provide Tail-Log backup, initiate cutover in DMS and 3 change the application connection strings Subnet used for DMS SMB Network Share 1 On-premises

24.Thank You Wayne Smith Cloud Solutions Architect waynesm@Microsoft.com