Bulk Import of DTS into SSIS legacy

  • We are migrating from 2000 to MSSQL 2005. Database got migrated well, cubes I suppose too.

    But with DTS its a different story.

    We installed 2005, mounted the DB, and now we need to grab all the DTSs and wack them in the lecacy of the 2005.

    I found a script which allows saving all the packages on HDD in one go.

    But then how do we now imsert them in MSSQL 2005? I know how to do it manually, I did one or two, but there are two problems:

    1. We have hundreds of DTSs and it will take me weeks clicking and making sure they are there.

    2. Management Studio 2005 has a bug. When you import one DTS manually by rightclicking and selecting Import, it does it and resets the tree selection (collapses the current selection) so that I have to expand the tree again manually. What da..?

    Please whoever did bulk import, please hep me out!

    Valentin

    M.Sc.IT, M.B.A, MCTS BI 2008, MCITP BI 2008, MCTS SQL Dev, CSM, CDVDM

  • I cannot believe none of the people here had the same problem.

    Please help me

    M.Sc.IT, M.B.A, MCTS BI 2008, MCITP BI 2008, MCTS SQL Dev, CSM, CDVDM

  • Have you tried DTSBackup? I think I got that to work when I was doing a migration...

    Kindest Regards,

    Frank Bazan

  • It definately works... just tried it again and can load multiple packages from file, local storage or dtsbackup format.

    Kindest Regards,

    Frank Bazan

  • This worked for me!! Thanks dudes!!!! :smooooth:

    ps: M$ made a very good effort to discourage people from using DTS in MSSQL2005 -- you cannot create packages, when you add/delete a DTS file you do it one-by-one and it throws the leftnav to the root of the tree, which would freak anyone out.

    M.Sc.IT, M.B.A, MCTS BI 2008, MCITP BI 2008, MCTS SQL Dev, CSM, CDVDM

  • Yeah, I remember when we completed our migration to 2K5, we had to run one machine on 2000 just so we could fix or change any DTS packages that were moved to the new servers. A real pain, especially as we had our DTS packages performing logic that couldn't be achieved on SSIS...

    Kindest Regards,

    Frank Bazan

  • Thanx for the help, I am in your boat now 🙂

    My job now is to migrate the whole damn thing onto 2005 from 2000. They would not go now for 2008 for the same reason they did not go for 2005 in late 2004, when they chose to use MS2000 - the product was too immature. Now they are paying for it.

    We have hundreds of DTS packages calling eachother, migrating hundreds of tables from AS400 onto MS and rebuilding cubes. Also heaps of dimensions and cubes, and a whole load of stored procedures and tables.

    I saw people searching on the net for a script or something which they could start from when preparing the migration job. Do you know of and have any script/migration doc, which describes the steps, hidden and common traps that could be encountered etc?

    Cheers,

    VAL

    M.Sc.IT, M.B.A, MCTS BI 2008, MCITP BI 2008, MCTS SQL Dev, CSM, CDVDM

Viewing 7 posts - 1 through 6 (of 6 total)

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