Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Sql server Integration Services 2008-2005 compatibility

I recently developed an SSIS package on my dev machine using the 2008 version. Later I foud the customer had Sql server 2005 and doesn't plan to upgrade anytime soon.

Is there a way to turn the 2008 package into a SSIS 2005 package, like a downgrade wizard?

like image 383
Nicolas De Irisarri Avatar asked Dec 17 '09 20:12

Nicolas De Irisarri


People also ask

Is it possible to run SSIS 2005 and SSIS 2008 package on the same server at the same time?

Best guess would be no. The engine to run the SSIS package would have to match the release level of the code. You have not been able to run any SSIS package on any release level below the developed level of the package (i.e. 2005 server will not run a 2008 package etc.)

What are the different versions of SSIS available?

SSIS can be used on all SQL Server 2005, 2008, 2008 R2, 2012, 2014 and 2016 editions except Express and Workgroup.

How do I find the SQL Server Integration Service version?

Determine the version of SQL Server Client tools To determine which versions of the client tools are installed on your system, start Management Studio, and then click About on the Help menu.


2 Answers

Courtesy of an unnamed source we have an app to downgrade a SSIS package from the 2008 version to 2005.

Whilst it works with the common components any new components aren’t supported with the exception of the Lookup.

3rd party components are also not supported.

It was gone through very limited testing and is not a supported option from MS. Its is not advised to use this for production packages.

It is a useful tool to get you out of a sticky situation.

http://ssisdowngrade.codeplex.com

like image 65
lstanczyk Avatar answered Nov 15 '22 21:11

lstanczyk


There may be components and properties available on 2008 that are not available on 2005. This is what makes the conversion so difficult.

However if your package is simple and fairly standard then the following might help. It worked for an empty package. I created one on 2008 and then attempted to open it in 2005. I got errors (of course). So I then copied the 2008 version and opened it in a plain text editor.

I then manually edit the file

1. Change the following

<?xml version="1.0"?><DTS:Executable xmlns:DTS="www.microsoft.com/SqlServer/Dts" DTS:ExecutableType="SSIS.Package.2">

to

<?xml version="1.0"?><DTS:Executable xmlns:DTS="www.microsoft.com/SqlServer/Dts" DTS:ExecutableType="SSIS.Package.1">

2. Change the following

<DTS:Property DTS:Name="PackageFormatVersion">3</DTS:Property>

to

<DTS:Property DTS:Name="PackageFormatVersion">2</DTS:Property>

3. Remove the following:

<DTS:Property DTS:Name="LastModifiedProductVersion">10.0.1600.22</DTS:Property>

4. Change the following:

<DTS:Property DTS:Name="CreationName">SSIS.Package.2</DTS:Property>

to

<DTS:Property DTS:Name="CreationName">MSDTS.Package.1</DTS:Property>

This works for an empty package, but I can make no guarantees for any other. Hope this helps

like image 42
James Wiseman Avatar answered Nov 15 '22 22:11

James Wiseman