Most SQL Server environments have more jobs, schedules, and hidden complexities than you realise. It’s only when you arrive at a migration and peek under the hood that the scale is clear.
Here we’ll pull out details from
msdbto give a clear snapshot of what you’ll actually be dealing with. If you don’t understand the effort upfront, the migration will expose it.
The thrust of Andy’s post covers migration, but I think it’s a good query to run simply to get a better understanding of all of the jobs in your environment.