DTS package import

  • Hi,

    I need to import 150 DTS packages in sqlserver2005.Importing one by one shouls take lot of time.

    how to import all these packages at a time.

    can you please provide the query.

    Thanks in advance.

  • Since it is not guaranteed that all of the packages will properly convert, you will need to investigate the packages at the individual level. Are you sure that you will even need all 150 packages? Are any of them deprecated?

    Hunker down and just start doing it.

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events

  • yes i need all the packages.

  • I think I used "DTSBackup2000" tool. Free download, and pushed 100+ DTS packages from 2000 to 2005 with just a few clicks.

  • Yes, there are tools available. With our dts packages we see about a 50% conversion failure rate and have to manually do the conversion anyway.

    One such tool that can do conversions

    http://www.pragmaticworks.com/products/Business-Intelligence/dtsxchange/

    ssis tutorial

    http://bi-polar23.blogspot.com/2008/03/new-to-ssis-start-here.html

    Conversion Article

    http://www.sqlmag.com/Article/ArticleID/94095/sql_server_94095.html

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events

  • Are you wanting to import and convert to SSIS at the same time ? The tool I referred to just imports them as DTS running in Legacy mode.

  • Hi I am trying to copy DTS Packages from sql 2000 to 2005? what is the process i can do it?

  • sureshdeenu (12/5/2009)


    Hi I am trying to copy DTS Packages from sql 2000 to 2005? what is the process i can do it?

    As I recall, you can export & import them one at a time, or try the tools mentioned above.

  • can u pls give me step by step to copy the packages from sql 2000 to 2005

  • I tried to move each dts package, rt. click on it-> Open -> Save as storagefile on source server(2000)

    On the destination server(2005), rt click on DTS package folder-> Import -> select the dts package storage file from the shared folder. But i couldnt open the package in destination server. wht is the best sollution for me?

  • 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!!!

  • Try Using DTSBACKUP TOOL

  • thanks, gud idea

  • 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.

  • 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.

Viewing 15 posts - 1 through 15 (of 17 total)

You must be logged in to reply to this topic. Login to reply