SQL Modernization Journey with Tools, Assets & Migration Best Practices
summary
Overview of tooling and hard numbers for moving SQL to Azure: Azure Migrate discovery finds metadata and produces a business case and a SQL assessment (example output shows 12,218 instances with 68 recommended for VM, 133 for MI, 17 for SQL DB). Migration paths use Azure Database Migration Service (offline for SQL DB, online for MI/VM), a new schema-migration step, and integration runtimes. Complex moves use staged backups, Data Box and striping or a spark-based IP for parallel loads; example: 22 TB moved with ~24 minutes downtime and ~1 TB per 3 hours throughput.
AI-written summary · about
chapters (5)
- 0:00SQL modernization intro
- 10:59Azure DMS overview
- 27:18DMS assessment & sizing
- 37:18Migration patterns & scenarios
- 48:14Resources & closing
related talks
57mDe-risk Your Azure SQL Migration: 5 Critical Considerations
46mSQL Migrations to Azure Made Easy
50mMigrating data solutions to the cloud - a checklist.
56mMigrate Databases to the Cloud - Why, How and Best Practices
50mSQL Server to Azure SQL: Performance and Availability
01h 02mLearn Live: Migrate SQL workloads to Azure Managed Instances
49mIt keeps getting easier to move Oracle and Open Source workloads to Azure
16mTo Azure SQL Database from SQL Server 2008
