August 18, 2005 at 7:00 am
I have a win2000 server that had sql server on it, it died.... I have been able to pull the hd out of the box and set it up as a slave and access the data on the drive. So I've moved the data files off. What I need at this point are the DTS packages that were in that instance of SQL Server. Where are they? How can I get to them with out Sql Server actually running??
Thanks, B
August 18, 2005 at 7:03 am
backup msdb and restore it to the new server.
August 18, 2005 at 7:55 am
so you think if I just move the msdb to the new server and then detach the original and then attach the one from the fried server my DTS packages will be there ?
August 18, 2005 at 8:04 am
they should... try just swapping the files.
Close the server and rename its msdb files to msdbold.mdf... then copy the old db's file and restart the server. Another user did the same thing yesterday with all the system dbs and it worked.
August 18, 2005 at 8:09 am
SWEET!!
I can't try it till this evening, but if it works I'll let you know either late tonight or tomorrow.
Thanks for the quick response.
I appreciate it.
B
August 18, 2005 at 8:14 am
HTH.
August 19, 2005 at 8:01 am
Substituting the other msdb may work, but you probably want to get the DTS packages out of it so you can put the original msdb back. You might have maintenance plans, agent jobs, or other DTS packages you don't want to lose.
Andy Warren wrote an article that will show you how to copy the DTS packages to another server.
http://www.sqlservercentral.com/columnists/awarren/copyingdtspackagestoadifferentserver.asp
If you attached the old msdb as another name, the code it that article could be modified to extract the DTS packages from it and save them on the server without interfering with the existing msdb.
August 29, 2005 at 9:51 am
Update:
I went ahead and just moved my files from the original DB to the new server. I only need the data files and the DTS packages, as I didn't have any jobs to worry about. This went with out a hitch. I restarted the sql server and woohoo my databases fired right up and I was able to see my DTS packages.
Having said that, I then tried to run my app that uses a DTS package, well, it failed. So what I then determined was the problem was the machine name. So I found a little sp provided by MS ( I believe) I ran it, renamed the instance to the new machine name, ran my app. No problems since. Been working fine almost a week now.
Thanks for the help.
B
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply