Azure Best Practices for Lift and Shift
summary
Migrating on-prem SQL Server to Azure VMs focuses on storage and throttles not buzzwords: premium disks tie size to performance (often forcing a 1 TB purchase), a P30 ≈ 500 IOPS and 125 MB/s at 256 KB blocks, and Azure enforces limits every 50 milliseconds, causing latency when IOPS or throughput hit caps. Use the ephemeral temp SSD for tempdb via a boot PowerShell + dbatools script, separate data/log/temp disks, monitor with PerfMon and Azure Monitor, and expect latency improvements (example: log disk change from ~128 ms to ~3.8 ms).
AI-written summary · about
chapters (8)
- 0:00Start
- 26:37put in a single large disk
- 27:47setting up your new servers
- 31:28using premium ssds
- 34:29identify all the applications
- 35:44set your caching
- 36:17set up your temp db boot script
- 48:47performance monitoring on sql azure
related talks
49mSQL Server on Azure VM - Configuring for Price-Performance
56mMigrate Databases to the Cloud - Why, How and Best Practices
50mSQL Server to Azure SQL: Performance and Availability
42mSQL Server on Azure VM - Configuring for price-performance
51mFly at Mach-speed with Azure SQL Managed Instance- 51mFly at Mach-speed with Azure SQL Managed Instance
51mAzure SQL Hyperscale Deep Dive
50mSQL Modernization Journey with Tools, Assets & Migration Best Practices