it is in the msdb database. just restore the msdb database to get it back. Since this is usually unacceptable to do on a prod machine, and i wouldnt recomend it just for this anyhow. HAve a second machine if you can with the same version. then restore it there and save it back over to the machine it was deleted from.
Thanks for the response. Here is how I fixed the problem.
Pulled a backup from the previous day of the MSDB database and made it a new temp database called Restore_MSDB.
I then went into the sysdtspackages table in the restore_MSDB and inserted all the records for the name of the Local Package back into the MSDB database.
It was alot easier than I thought. The key is to insert all historical records for the Local Package name since I guess that table stores incremental changes from the first time it was created.
You would be better off saving and loading packages from structured storage files then you can use a file backup to save them - makes moving and releasing simpler too.
If you want to save in msdb then I would add a job to save them daily to a directory which is backed up.
I also include a job to script properties so I can save it in sourcesafe and see what has changed.
======================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.