De-risk Your Azure SQL Migration: 5 Critical Considerations
summary
Research shows more than 80% repatriate at least one workload; migrations fail from misaligned goals, unexpected CPU/storage/IOPS costs and chatty apps. Assessment steps include inventory, benchmark before/after, data lineage and archive cold rows to reduce storage. Use Database Migration Assistant, MAP Toolkit, Azure Database Migration Service and Azure Data Box for transfer; note backup restore only to Managed Instance. Pilot small, refactor queries and indexes, test data fidelity with parallel runs, enable Azure Cost Management and monitoring (or SentryOne/SentryOne Test/SentryOne Doc) to catch surprises.
AI-written summary · about
chapters (23)
- 0:00Start
- 2:08Why Migrations Fail
- 6:35Performance and Cost
- 11:22True Benefits of the Cloud
- 12:11Legal Compliance and Auditing Requirements
- 14:24True Benefits of Moving to the Cloud
- 17:07Consolidation and Consolidated Management and Cost Management of Data Storage
- 19:21Beware the Executive
- 20:08Coding Standards
- 21:29Backup Strategy
- 22:43Legacy Entanglements
- 24:25Need for Speed
- 26:46Is the Data Clean
- 31:34Re-Architecting
- 33:50Data Lineage Analysis
- 34:12Impact Analysis
- 35:17Free Tools
- 37:58Data Database Migration Assistant
- 38:57Advanced Threat Detection
- 44:33The Azure Database Migration Service
- 45:37Test Your Data for Fidelity
- 48:11Baselines
- 51:48Azure Monitor
related talks
50mMigrating data solutions to the cloud - a checklist.
50mSQL Modernization Journey with Tools, Assets & Migration Best Practices
56mMigrate Databases to the Cloud - Why, How and Best Practices
01h 02mLearn Live: Migrate SQL workloads to Azure Managed Instances
49mIt keeps getting easier to move Oracle and Open Source workloads to Azure
46mSQL Migrations to Azure Made Easy
54mAzure Best Practices for Lift and Shift
44mAccelerate your Oracle & Mainframe Modernization journey to Azure SQL