DTS disaster recovery

Can anyone recommend any best practices for restoring local packages? In a
disaster recovery situation I will have 1 SQL Server box rather than 4 so I
won't be able to restore all of my local packages by restoring MSDB. Any
thoughts?
In the same situation, I would restore the MSDB databases from each server
as MSDB1, MSDB2, etc, then move the data into the main MSDB database...
Also, save out each DTS package as a Structured Storage file and dump that
into a version control application such as Source Safe.
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"Terri" <terri@.cybernets.com> wrote in message
news:dml9p8$vqu$1@.reader2.nmix.net...
> Can anyone recommend any best practices for restoring local packages? In a
> disaster recovery situation I will have 1 SQL Server box rather than 4 so
> I
> won't be able to restore all of my local packages by restoring MSDB. Any
> thoughts?
>
|||"Kevin3NF" <KHill@.NopeIDontNeedNoSPAM3NF-inc.com> wrote in message
news:evifdFg9FHA.2792@.TK2MSFTNGP11.phx.gbl...
> In the same situation, I would restore the MSDB databases from each server
> as MSDB1, MSDB2, etc, then move the data into the main MSDB database...
Would anyone have any code that would select and insert this data.

> Also, save out each DTS package as a Structured Storage file and dump that
> into a version control application such as Source Safe.
Does this need to be done with the GUI?
More generally would named instances help here?