Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have some new SQL 2008 SSIS jobs that were recently developed, mostly to do some simple flat-file loading and targeting a set of tables on a 2008 server.

As it turns out, they may have to run on a SQL 2005 server for both the SSIS and target tables.

Is it possible to downgrade the packages somehow, instead of redeveloping them from scratch?

Obviously any 2008 specific SSIS features would disappear; but it would be nice to not start with a blank designer screen.

share|improve this question
up vote 4 down vote accepted

SSIS Downgrade should do exactly what you need.

share|improve this answer

A second option would be to run the SSIS packages on ServerA2008 and set the connection managers for your source/destination to be ServerB2005. No code change required and you should be able to continue using the 2008 features.

One caveat to this approach is it will not work if you use the "SQL Server Destination" component as it requires the package be executed on the same machine as the destination.

share|improve this answer
thanks....but our server is in DMZ – Manjot Aug 29 '11 at 21:09

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.