Sql-server – How to script SQL Server Jobs for migration

Follow the directions in this article. It has to do with the suspect database caused by a missing or new device. I hope this helps.

If that doesn't work, you will have to recreate the MSDB database yourself.

1. Detach the damaged msdb. You can't just detach msdb because you're not allowed to detach system databases. However, you can if you start the server with trace flag 3608. I did this by shutting down the server, navigating to the directory 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn' and doing the following: start sqlservr.exe -c -T3608
2. Move or rename the damaged msdb files (msdbdata.mdf and msdblog.ldf in the 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data' directory)
3. Run the instmsdb.sql script in the 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install' directory
4. Shutdown and restart the server without the 3608 trace flag

In SSIS there's an SSIS task that can transfer all jobs, or just specific jobs. You can tell it to overwrite the jobs, or fail if they exist, and handle the job deletion your self. Schedule this as a job to run nightly, or make it a part of your job release process to run this job after a job has been changed.

You'll want to add a SQL task after the jobs have been transferred to disable them using the procedures in the msdb database.