I'm considering moving a SQL Server database from a virtual machine to a managed Azure SQL PaaS option. Is there a reliable tool or assessment method for comparing the real costs? The Azure pricing calculator seems to underestimate the eventual bill, especially for storage and related charges. I'd prefer something based on the workload rather than just entering estimates manually.
2 Answers
Try to compare more than just the compute line item. A PaaS database can look more expensive at the same tier, but the price usually includes things you would otherwise manage separately on a VM, such as backups, patching, and high availability. On the other hand, PaaS gives you less flexibility over the CPU, memory, and storage combination. With some managed instance configurations, storage growth can force you into a larger and much more expensive compute tier.
Azure Arc’s SQL Server migration assessment is probably the best starting point. It analyzes the workload, recommends a suitable Azure SQL target and configuration, and provides retail pricing for the suggested setup. It also highlights migration risks and runs automatically on a recurring schedule. The assessment is free for SQL Server editions.
The development team is worried that PaaS will cost more, so I’m trying to produce a realistic comparison. CPU usage rarely reaches 50%, and I may be able to reduce the SKU while keeping the required memory. My main problem is making sure the calculator assumptions match our actual storage and usage.