Baselining your SQL Server Workload for an Azure SQL Migration
Tim Radney
If you are planning a migration to Azure, or anywhere else, it is imperative that you know the baseline of your existing workload. Capturing certain metrics are straight forward, such as CPU, memory, and disk size, but what about storage I/O? Sure latency is an important metric to monitor, but are you capturing throughput as well?
Resource limits in Azure vary between virtual machines, Azure SQL Database, Azure SQL Managed Instance, and Hyperscale. It is important to know the difference in order to size your workload properly in these environments and it isn’t baselining your existing infrastructures capabilities, it is baselining what your existing workload needs.
In this session, you’ll learn about the differences in the different Azure SQL offerings and tiers, as well as how to capture these baselines in your existing environment. You’ll also get first hand accounts of various customer engagements where this detail was missed during the planning phase.
Get the Latest
Sign up to stay up to date with news, special announcements and educational content.
Redgate will only contact you about PASS Data Community Summit (in line with our Privacy Policy) unless you separately request emails about Redgate. You can unsubscribe from these updates at any time.
Thanks for submitting! We'll be in touch soon.
