locked
Migrating SSIS 2005 TO SSIS 2008 RRS feed

  • Question

  • What are best practices for moving/exporting SQL Server Integration Services Packages from a SQL Server 2005 DB over to 2008?

    What are the common problems facing when migrating?

    Tuesday, August 17, 2010 12:50 AM

Answers

  • The main issues i've encountered are in the Script Transformations - sometimes scripts just don't move, or don't migrate properly.

    Otherwise it's pretty painless as there weren't too many changes from 2005 to 2008. Just open your 2005 project in BIDS2008, open the packages and let it convert them for you.

    Cheers, James


    James Beresford @ www.bimonkey.com
    SSIS / MSBI Consultant in Sydney, Australia
    SSIS ETL Execution Control and Management Framework @ SSIS ETL Framework on Codeplex
    Tuesday, August 17, 2010 1:04 AM
  • the easiest way is to open a the toolbox in BIDS2008 and drag and drop a scrip component object and while opening the package with BIDS2005 just cut and past the code and set the variables, thats how i do it.

    but you have to have BIDS2005 and BIDS2008 (you dont need to have them on the same machine).


    Sincerely SH -- MVP, MCITP 2008, MCTS 2008 & 2005 -- Please kindly mark the post(s) that answered your question and/or vote for the post(s).
    Tuesday, August 17, 2010 4:56 PM

All replies

  • The main issues i've encountered are in the Script Transformations - sometimes scripts just don't move, or don't migrate properly.

    Otherwise it's pretty painless as there weren't too many changes from 2005 to 2008. Just open your 2005 project in BIDS2008, open the packages and let it convert them for you.

    Cheers, James


    James Beresford @ www.bimonkey.com
    SSIS / MSBI Consultant in Sydney, Australia
    SSIS ETL Execution Control and Management Framework @ SSIS ETL Framework on Codeplex
    Tuesday, August 17, 2010 1:04 AM
  • Yes, when i upgrade the package from 2005 to 2008.

    there is an script task error came.

    here the warning is:

    TITLE: Microsoft Visual Studio

    ------------------------------

     

    Warning at Script Task [Script Task]: Found SQL Server Integration Services 2005 Script Task "ScriptTask_a51820e8c1b54e4f9d0aaf8857809cf8" that requires migration!

     

    Warning at DeleteFiles []: Succeeded in upgrading the package.

     

     

     

     

    ------------------------------

    BUTTONS:

     

    OK

    ------------------------------


    Tuesday, August 17, 2010 2:53 PM
  • the easiest way is to open a the toolbox in BIDS2008 and drag and drop a scrip component object and while opening the package with BIDS2005 just cut and past the code and set the variables, thats how i do it.

    but you have to have BIDS2005 and BIDS2008 (you dont need to have them on the same machine).


    Sincerely SH -- MVP, MCITP 2008, MCTS 2008 & 2005 -- Please kindly mark the post(s) that answered your question and/or vote for the post(s).
    Tuesday, August 17, 2010 4:56 PM
  • Hello,

    Check the following article Upgrading Integration Services Packages to know various options.

    Cheers,
    Ashish

     

    Tuesday, August 17, 2010 5:14 PM