|
sql
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Help on Sql Server 2005 job steps lost
I had to reinstall my sql server 2005.
After that I copied the old master database to the new installation. Everything is working, but I lost the job steps. I have the old jobs, ma inside each one I have no steps. Someone can Help me. Thanks a lot. Roberto Roberto,
Jobs are defined in msdb. If you copied your msdb to the new installation you should have got those as well. If it is not too late, try that. Otherwise, you could restore the old msdb as msdbold and try copying data from msdbold to msdb. (But I have never done that.) Whatever you do, once you get the jobs, you should script them all out and save the script. Every possible object, job, etc. that you put on your SQL Server should also be in source control. (For just such an emergency.) RLF Show quoteHide quote "Roberto Rasto" <rastorobe***@hotmail.it> wrote in message news:gih6js$vfp$1@nnrp.ngi.it... >I had to reinstall my sql server 2005. > After that I copied the old master database to the new installation. > Everything is working, but I lost the job steps. > I have the old jobs, ma inside each one I have no steps. > > Someone can Help me. > Thanks a lot. > > Roberto > So, what would I actually do if I could not simply restore or attach the old
msdb? 1. Install a scratch server. (SQL Express if the msdb is less that 4GB.) 2. Script out the jobs. SQL Server Management Studio - Object Explorer window Server SQL Server Agent Jobs Now open the Object Explore Details Select all jobs, right click, Script Job as \ Create Save script 3. Run script on my new server. 4. Scratch the scratch server. FWIW, RLF Show quoteHide quote "Russell Fields" <russellfie***@nomail.com> wrote in message news:uLpEjtiYJHA.760@TK2MSFTNGP02.phx.gbl... > Roberto, > > Jobs are defined in msdb. If you copied your msdb to the new > installation you should have got those as well. If it is not too late, > try that. > > Otherwise, you could restore the old msdb as msdbold and try copying data > from msdbold to msdb. (But I have never done that.) > > Whatever you do, once you get the jobs, you should script them all out and > save the script. Every possible object, job, etc. that you put on your > SQL Server should also be in source control. (For just such an > emergency.) > > RLF > > > > "Roberto Rasto" <rastorobe***@hotmail.it> wrote in message > news:gih6js$vfp$1@nnrp.ngi.it... >>I had to reinstall my sql server 2005. >> After that I copied the old master database to the new installation. >> Everything is working, but I lost the job steps. >> I have the old jobs, ma inside each one I have no steps. >> >> Someone can Help me. >> Thanks a lot. >> >> Roberto >> >
Other interesting topics
|
|||||||||||||||||||||||