views:

820

answers:

3

Maybe a stupid question but... I created an SSIS package using VS2008 Professional. I want to deploy and execute it on a server running SQL Server 2005. When I try to run it I get an error stating the version of the Execute Package Utility on the server is different than the version of the package I'm trying to execute (makes sense, since I created the package with the newer version of VS).

To my knowledge Microsoft doesn't simply provide a download of the EPU to "upgrade" it, so how do I execute the package on a server that's running the previous version of SQL Server? Do I need to install a "throwaway" copy of SQL 2008 just to update the package, or what? On my workstation (which has VS2008) it runs fine against SQL 2005.

+1  A: 

You can try installed the Express edition of SQL Server 2008 and see if the included dtexec will work. Unfortunately, the configuration you are attempting to run is not supported and will likely incur errors.

Cadaeic
Really? So i guess they assume you will only ever use VS2008 with SQL 2008? Or is there some way I am missing to use .Net 3.5 but a .net 2.0 ssis package?
Wayne M
+3  A: 

Unfortunately, you can't do this. It makes no sense since you can run SSIS against different databases (what if you were running a package on a server that didn't even use SQL Server?) but you'll get that version error if you created it in BIDS 2008.

Jack Of Hearts
A: 

As I'm about to embark on the same type of project, so the solution seems to be to use VS2005 to create the SSIS package, and and do the deployment. The package is still executable through our VS2008 code, but just can't create/deploy to 2005.

WHY?! OH WHY!? :(

ElHaix