Downgrade SSIS 2008 package to 2005

  • I developed and tested 3 .dtsx packages in my development environment using Visual Studio 2008 v9.0.30729.4462 QFE, not realising that the servers these packages should be run on are still SQL server 2005. How do I make these packages created using Visual Studio 2008 with SQL Server Integration Services installed run on SQL server 2005 ?

    The error messages I get when trying to execute the packages on SQL 2005 are:

    The version number in the package is not valid. The version number cannot be greater than current version number.

    Package migration from version 3 to version 2 failed with error 0xC001700A "The version number in the package is not valid. The version number cannot be greater than current version number".

    Error loading value "<DTS:Property xmlns:DTS="www.microsoft.com/SqlServer/Dts" DTS:Name="PackageFormatVersion">3</DTS:Property>" from node "DTS:Property".

    The servers can not be upgraded to SQL 2008, so I need a way to get my packages saved in a format acceptable for SQL 2005.

    Thanks a lot.



    Posting Data Etiquette - Jeff Moden[/url]
    Posting Performance Based Questions - Gail Shaw[/url]
    Hidden RBAR - Jeff Moden[/url]
    Cross Tabs and Pivots - Jeff Moden[/url]
    Catch-all queries - Gail Shaw[/url]


    If you don't have time to do it right, when will you have time to do it over?

  • I am afraid that there is no way of doing this other than manually recreating the packages in 2005.

    If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

  • 2008 does not support backward compatability, so you can do this. You need to do the re work using visual studio 2005.

  • Thanks for your responses. I managed to downgrade the packages. I need to thank a colleague -with great Google skills- for this, who sent me this link that references a little application SSISdowngrade on CodePlex[/url] doing most of the work downgrading a 2008 .dtsx package to 2005.

    After running my packages through this application I could still not open the packages. So I opened up the packages in an xml editor and removed all references to system variable "System::ProductVersion", which apparently is not known in 2005. Plus I changed the connection string to my SQL database to use "SQLNCLI.1" for the Provider instead of "SQLNCLI10.1".

    After doing this I could succesfully open the .dtsx files in Visual Studio 2005 / SQL server 2005. Only the encryption of the ftp password was still reported as an error, but that was easily solved by opening the package in Visual Studion 2005 and setting a new password.

    Thank you Jasmin for saving my day.



    Posting Data Etiquette - Jeff Moden[/url]
    Posting Performance Based Questions - Gail Shaw[/url]
    Hidden RBAR - Jeff Moden[/url]
    Cross Tabs and Pivots - Jeff Moden[/url]
    Catch-all queries - Gail Shaw[/url]


    If you don't have time to do it right, when will you have time to do it over?

  • Thanks for posting back - I'd never heard of that.

    If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

  • R.P.Rozema (1/12/2011)


    Thanks for your responses. I managed to downgrade the packages. I need to thank a colleague -with great Google skills- for this, who sent me this link that references a little application SSISdowngrade on CodePlex[/url] doing most of the work downgrading a 2008 .dtsx package to 2005.

    After running my packages through this application I could still not open the packages. So I opened up the packages in an xml editor and removed all references to system variable "System::ProductVersion", which apparently is not known in 2005. Plus I changed the connection string to my SQL database to use "SQLNCLI.1" for the Provider instead of "SQLNCLI10.1".

    After doing this I could succesfully open the .dtsx files in Visual Studio 2005 / SQL server 2005. Only the encryption of the ftp password was still reported as an error, but that was easily solved by opening the package in Visual Studion 2005 and setting a new password.

    I wonder what the Downgrade tool does, since you still had to manually intervene for the ProductVersion and edit the connectionstrings.

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • I wonder what the Downgrade tool does, since you still had to manually intervene for the ProductVersion and edit the connectionstrings.

    Sounds to me like a self-nomination for a mini research project in your spare time 🙂

    If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

  • Phil Parkin (1/12/2011)


    I wonder what the Downgrade tool does, since you still had to manually intervene for the ProductVersion and edit the connectionstrings.

    Sounds to me like a self-nomination for a mini research project in your spare time 🙂

    Hehe. 🙂

    No.

    😀

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • Source code is available on codeplex, so you can see for yourself what it does. I don't care I had to do some things manually, I am still very thankful to the author. (S)he correctly saw that more people ran into the same issue and shared her/his knowledge.



    Posting Data Etiquette - Jeff Moden[/url]
    Posting Performance Based Questions - Gail Shaw[/url]
    Hidden RBAR - Jeff Moden[/url]
    Cross Tabs and Pivots - Jeff Moden[/url]
    Catch-all queries - Gail Shaw[/url]


    If you don't have time to do it right, when will you have time to do it over?

  • A big THANK YOU to the downgrade application author!

  • Thank you very much for the great application.

    Now, works out of the box - No changes required :-D. My DBA is really happy.

  • Awesome aplication !

  • Thanks to the author of the downgrade package. Saved me a lot of work and luckily i had to make no changes at all:-)

  • Thank you for this post. Just saved the day for me (downgraded SSIS package from 2008 to 2005 successfully!)

Viewing 14 posts - 1 through 14 (of 14 total)

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