SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Downgrade SSIS 2008 package to 2005


Downgrade SSIS 2008 package to 2005

Author
Message
R.P.Rozema
R.P.Rozema
Ten Centuries
Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)

Group: General Forum Members
Points: 1125 Visits: 1685
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 "<DTSTongueroperty xmlnsBigGrinTS="www.microsoft.com/SqlServer/Dts" DTS:Name="PackageFormatVersion">3</DTSTongueroperty>" from node "DTSTongueroperty".



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
Posting Performance Based Questions - Gail Shaw
Hidden RBAR - Jeff Moden
Cross Tabs and Pivots - Jeff Moden
Catch-all queries - Gail Shaw


If you don't have time to do it right, when will you have time to do it over?
Phil Parkin
Phil Parkin
SSCoach
SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)

Group: General Forum Members
Points: 19027 Visits: 20461
I am afraid that there is no way of doing this other than manually recreating the packages in 2005.


Help us to help you. For better, quicker and more-focused answers to your questions, consider following the advice in this link.

If the answer to your question can be found with a brief Google search, please perform the search yourself, rather than expecting one of the SSC members to do it for you.

Please surround any code or links you post with the appropriate IFCode formatting tags. It helps readability a lot.
sharath.chalamgari
sharath.chalamgari
SSCommitted
SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)

Group: General Forum Members
Points: 1520 Visits: 798
2008 does not support backward compatability, so you can do this. You need to do the re work using visual studio 2005.
R.P.Rozema
R.P.Rozema
Ten Centuries
Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)

Group: General Forum Members
Points: 1125 Visits: 1685
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 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:TongueroductVersion", 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
Posting Performance Based Questions - Gail Shaw
Hidden RBAR - Jeff Moden
Cross Tabs and Pivots - Jeff Moden
Catch-all queries - Gail Shaw


If you don't have time to do it right, when will you have time to do it over?
Phil Parkin
Phil Parkin
SSCoach
SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)

Group: General Forum Members
Points: 19027 Visits: 20461
Thanks for posting back - I'd never heard of that.


Help us to help you. For better, quicker and more-focused answers to your questions, consider following the advice in this link.

If the answer to your question can be found with a brief Google search, please perform the search yourself, rather than expecting one of the SSC members to do it for you.

Please surround any code or links you post with the appropriate IFCode formatting tags. It helps readability a lot.
Koen Verbeeck
Koen Verbeeck
One Orange Chip
One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)

Group: General Forum Members
Points: 27883 Visits: 13268
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 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:TongueroductVersion", 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.


How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?
My blog at SQLKover.

MCSE Business Intelligence - Microsoft Data Platform MVP
Phil Parkin
Phil Parkin
SSCoach
SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)

Group: General Forum Members
Points: 19027 Visits: 20461
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 :-)


Help us to help you. For better, quicker and more-focused answers to your questions, consider following the advice in this link.

If the answer to your question can be found with a brief Google search, please perform the search yourself, rather than expecting one of the SSC members to do it for you.

Please surround any code or links you post with the appropriate IFCode formatting tags. It helps readability a lot.
Koen Verbeeck
Koen Verbeeck
One Orange Chip
One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)

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

:-D


How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?
My blog at SQLKover.

MCSE Business Intelligence - Microsoft Data Platform MVP
R.P.Rozema
R.P.Rozema
Ten Centuries
Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)

Group: General Forum Members
Points: 1125 Visits: 1685
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
Posting Performance Based Questions - Gail Shaw
Hidden RBAR - Jeff Moden
Cross Tabs and Pivots - Jeff Moden
Catch-all queries - Gail Shaw


If you don't have time to do it right, when will you have time to do it over?
Mshivaram
Mshivaram
Forum Newbie
Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)

Group: General Forum Members
Points: 7 Visits: 49
A big THANK YOU to the downgrade application author!
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