Lessons learned from moving to Microsoft Azure THR2069 Lessons learned from moving to Microsoft Azure Denny Cherry Denny Cherry & Associates Consulting mrdenny@dcac.co

Denny Cherry Principle Consultant Working with SQL Server for 20+ years Working with Azure since its release Microsoft Gold Partner is Data Platform and Cloud Platform Gold Winner for Data Center Innovations for 2017 Golden Bridge awards for an Azure Migration we completed

Moving an existing data center to Azure Agenda Moving an existing data center to Azure Converting a Monolithic Application to PaaS

Moving an existing data center to Azure

Moving an Existing Data Center to Azure A new client wanted to move their entire legacy data center to cloud Data center consisted of several traditional legacy applications which required migrations No applications were cloud ready Most technology was 10+ years out of date

10 years of 1st party applications which run the business “Legacy” Technology SQL Server 2005 SQL Server 2000 AX 4 Exchange 5.5 Windows 2003 Windows XP 10 years of 1st party applications which run the business

Migration Approach Combination of PaaS and IaaS was used Office 365 Outlook to replace Exchange SharePoint and OneDrive to replace File Servers SQL 2014 to replace SQL 2005 SQL DB to replace SQL 2000 Windows 2012 R2 to replace Windows 2003 Dynamics 365 to replace AX4*

Different Technologies for Different Problems Different applications had different problems Cloud has no one size fits all solution Each problem requires a slightly different solutions Legacy applications like AX4 can present unique challenges

How we did the migration Configured site to site VPN Built new Active Directory Domain Controllers SQL Server Log Shipping Built new web/application servers and reinstalled Pointed new web and application servers to new database server, completed database migration Changed Public DNS

The End Result COO was happy CFO was happy CEO was happy Cloud budget was 20% less than new hardware & software Final implementation was 10% less than budgeted COO was happy CFO was happy CEO was happy

Converting a Monolithic Application to PaaS

Existing Application Target 1TB database running in Azure DS13 VM Database Server CPU running at capacity Web tier running in VMs is hard to deploy to No control of data locality All data exists in SQL Server today

Biggest Challenges What to do with all the data? SQL DB Cosmos Azure Data Lake Make deployments easier Need continuous deployment Deployment method needs to include database solution Geo-locality Customer data needs to be in the customers region Customer needs to be in control Easy migration options

How we are doing the migration Moving authentication into its own database Work with end customers for Azure region selection Migrate LOB data into Azure Data Lake Build and populate new customer tables in authentication database Build and execute SSIS packages to move end customer data into PaaS SQL DB databases Build web app in various regions world wide to support customers. Deploy traffic manager in front of web apps. Migrate DNS from VM farm to traffic manager

The End Result Ask me next year So far it’s going well

Biggest takeaway for every project There is no one correct Azure solution Some projects need IaaS, some PaaS, some SaaS Some need a combination Some need all 3

Lessons learned from moving to Microsoft Azure THR2069 Lessons learned from moving to Microsoft Azure Denny Cherry Denny Cherry & Associates Consulting mrdenny@dcac.co

Please evaluate this session Tech Ready 15 6/26/2018 Please evaluate this session From your Please expand notes window at bottom of slide and read. Then Delete this text box. PC or tablet: visit MyIgnite https://myignite.microsoft.com/evaluations Phone: download and use the Microsoft Ignite mobile app https://aka.ms/ignite.mobileapp Your input is important! © 2012 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.

6/26/2018 12:05 PM © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.