Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


DTS package import


DTS package import

Author
Message
nba ninetytwo
nba ninetytwo
Grasshopper
Grasshopper (23 reputation)Grasshopper (23 reputation)Grasshopper (23 reputation)Grasshopper (23 reputation)Grasshopper (23 reputation)Grasshopper (23 reputation)Grasshopper (23 reputation)Grasshopper (23 reputation)

Group: General Forum Members
Points: 23 Visits: 350
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!!!
Arjun SreeVastsva
Arjun SreeVastsva
SSCrazy
SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)

Group: General Forum Members
Points: 2529 Visits: 1642
Try Using DTSBACKUP TOOL
sureshdeenu
sureshdeenu
SSC Rookie
SSC Rookie (46 reputation)SSC Rookie (46 reputation)SSC Rookie (46 reputation)SSC Rookie (46 reputation)SSC Rookie (46 reputation)SSC Rookie (46 reputation)SSC Rookie (46 reputation)SSC Rookie (46 reputation)

Group: General Forum Members
Points: 46 Visits: 287
thanks, gud idea
jezman
jezman
SSC Rookie
SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)

Group: General Forum Members
Points: 25 Visits: 129
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.
bradfordshultz
bradfordshultz
Grasshopper
Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)

Group: General Forum Members
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.
kissingharry
kissingharry
Grasshopper
Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)

Group: General Forum Members
Points: 14 Visits: 288
Try to install the backward compatability on sql server 2005,you can able to see the DTS packages in the 2005.
robert.wiley
robert.wiley
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
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
Jamie Ingram-729524
Jamie Ingram-729524
SSC Veteran
SSC Veteran (243 reputation)SSC Veteran (243 reputation)SSC Veteran (243 reputation)SSC Veteran (243 reputation)SSC Veteran (243 reputation)SSC Veteran (243 reputation)SSC Veteran (243 reputation)SSC Veteran (243 reputation)

Group: General Forum Members
Points: 243 Visits: 407
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.

Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search