|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Wednesday, September 26, 2012 3:44 AM
Points: 23,
Visits: 319
|
|
hi!!
try that:
1-make a backup of your msdb db. 2-restore it on your target server with another name(be carful!!!, don't overwrite on the true msdb on sql 2005) 3-excecute that in the msdb that you've restored:
use msdb_restored go
insert into msdb.dbo.sysdtspackages select * from sysdtspackages a where name in ('dts names....') and createdate =(select max(createdate)from sysdtspackages b where b.name in ('dts names....') and a.name=b.name)
enjoy!!!
|
|
|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: Wednesday, May 08, 2013 3:44 AM
Points: 2,173,
Visits: 1,350
|
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Sunday, April 08, 2012 10:08 PM
Points: 37,
Visits: 117
|
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: 2 days ago @ 7:33 AM
Points: 23,
Visits: 105
|
|
I learnt the hard way that importing existing packages was no short cut. By the time it was all up and running I wished we had rebuilt everything from scratch. Especially since a lot of the packages could have easily been replicated with some meta data and a looping container!
The barrier to this was that the existing DTS packages were "proven to work" and our project managers liked this, unfortunately the logic was flawed because they were not proven to work within SSIS. And in many cases they didn't! This route proved to be a massive false economy.
Obviously your situation may be entirely different, but I wish we had re-done the bulk of our packages - even if it had just been the more straight forward data shunting tasks.
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Friday, December 31, 2010 2:01 PM
Points: 11,
Visits: 101
|
|
if you dont/wont need to make any changes to the packages, use DTS Backup 2000 application (http://www.sqldts.com/242.aspx) and run the DTS in legacy mode on the 2005 server. Otherwise I'd use one of the many DTS Documentation tools and generate documentation for all my DTS packages. Then I'd sit down and start with number one and create an equivalent SSIS package until I'd done them all. Depending on your specific situation, there may be a shortcut/easier way to do it, but in my experience, you just have to end up rebuilding them all anyway.
Cheers and Good luck.
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Thursday, December 06, 2012 6:33 PM
Points: 14,
Visits: 246
|
|
| Try to install the backward compatability on sql server 2005,you can able to see the DTS packages in the 2005.
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Tuesday, May 03, 2011 10:13 AM
Points: 1,
Visits: 1
|
|
See if this helps you since it helped me. Specifically, I used the Package Migration wizard so click that link in this document to see if it helps you too.
http://msdn.microsoft.com/en-us/library/ms143496.aspx
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Friday, May 17, 2013 3:08 AM
Points: 205,
Visits: 261
|
|
If you just want to run the packages on the new server: Export your DTS packages using DTSBackup. Save them to a network location Create an SSIS job that calls the DTS packages.
Jamie
We are the pilgrims, master. We shall go always, a little further.
|
|
|
|