Last updated: August 28, 2026.
A job definition is only one part of migration. Job owners, credentials, proxies, linked servers, file paths, and databases must also exist on the destination.
Inventory jobs and schedules
USE msdb;
SELECT j.name AS JobName, SUSER_SNAME(j.owner_sid) AS OwnerName,
s.name AS ScheduleName, s.enabled AS ScheduleEnabled
FROM dbo.sysjobs AS j
LEFT JOIN dbo.sysjobschedules AS js ON js.job_id = j.job_id
LEFT JOIN dbo.sysschedules AS s ON s.schedule_id = js.schedule_id
ORDER BY j.name, s.name;Migration checklist
- Script jobs from SQL Server Management Studio.
- Set a valid low-privilege owner.
- Recreate credentials and proxies separately.
- Disable schedules until a manual test succeeds.
- Confirm alerting and job history retention.
Reference: Microsoft SQL Server Agent documentation.