You have two options

1. Try using sp_attach_db or sp_attach_single_file_db
2. Contact PSS and see if they can work their magic.

Do you not have backups ?

--

----------------------------
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org



"Dhaval" <dhaval.choksi (AT) in (DOT) iqara.net> wrote

Check this out http://www.sqldev.net/dts/SavePkgToFile.htm
You can take your DTS package from msdb database to file (Structured Storage
File [.dts])
If you already have your DTS package in file format, you can import it back
to your new server. You can do it manually by saving it one-by-one or you
can use my dts package for transfering DTS file into a server. I send the
dts package directly to your e-mail address. This dts package is
modification of dts I found in MOC.

You just have to modify the 'restore_dts.bat', change the 'D:\DTS\Update'
with your directory where you store your dts package files. And then run the
'restore_dts.bat'. The only limitation I've found in this dts package is it
can't import dts package which contain 'Process OLAP Cubes Task'. So please
remove your dts package which contain 'Process OLAP Cubes Task', or the
'restore_dts.bat' will run forever. If you have difficulties because of this
problem just e-mail me, I'll explain a hint to overcome this.

--
Hope it helps
Regards,
Jono Indrawijaya - MCDBA
PT. eBiz Cipta Solusi - Microsoft Certified Partner
Indonesia

"Dhaval" <dhaval.choksi (AT) in (DOT) iqara.net> wrote

I assume that you know that attaching msdb is not just straight like that
(it raise some issue), you can force this but do this in a dummy server just
to take out the dts package.

--
Hope it helps
Regards,
Jono Indrawijaya - MCDBA
PT. eBiz Cipta Solusi - Microsoft Certified Partner
Indonesia

"Jono Indrawijaya" <jono (AT) ebizcipta (DOT) com> wrote

Once the old msdb is online again either via a backup or attach kludge then
you can just use SQL-
insert into msdb..sysdtspackages select * from oldmsdb..sysdtspackages
This would save the intermediate file step.

Are you sure the problem with the OLAP task is not down to the destination
machine or the client used to open the package just not having the OLAP Task
installed? No other reason why an individual task should "break" the package
integrity.


--
Darren Green
http://www.sqldts.com

"Jono Indrawijaya" <jono (AT) ebizcipta (DOT) com> wrote

I was wondering if you guys have ever worked a DTS package to backup to
file your DTS packages. And also have a way to import them again?
Something I could say use in a stored procedure or in a DTS package its
self.

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Hi,

Firstly Thank you all for the reply.

The senario is the drive on which our mdf files were
stored has been crashed not all the data bases were
recoverd. I some how managed to restore the msdb file. but
it got in to supect mode. again i managed to copy the data
from sysdtspackages table into another table.

Now in this new server i have created the database that
were used in the dts. now what can i do. I am going to try
to use the textcopy.exe utility to make a .dts file and
import it again. is there any other way to get dts back.


regards
dhaval

If you have sysdtspackages in the form of a table beit in whatever database
then you should be able to insert it back into your proper sysdtspackages
table and go from there. I believe Darren in an article mentions this as a
technique though the medium is text file.



--

----------------------------
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org



"Dhaval Choksi" <dhaval.choksi (AT) in (DOT) iqara.net> wrote