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


Running SSIS 2005 Packages on SQL 2012 Instance


Running SSIS 2005 Packages on SQL 2012 Instance

Author
Message
atalders
atalders
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 10
Hi all--

We are going through the process of rationalizing our databases from SQL Server 2005 to 2012. In our development environment, however, we have many packages in SSIS 2005.

We plan on upgrading all of the packages from SSIS 2005 to SSIS 2012, but given the volume of packages necessary and certain standards we have to abide by when testing and deploying packages, it will take some time. (must be upgraded on local, then deployed to dev, then staging...)

My question is this: If I upgrade the engine and databases from SQL Server 2005 to SQL Server 2012, will my SSIS 2005 packages still execute properly with the SQL Server 2012 engine until we upgrade all of the SSIS packages from 2005 to 2012? Are there any caveats I should be aware of?

Thanks in advance!
Fraggle-805517
Fraggle-805517
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: 1083 Visits: 1512
atalders (5/8/2013)
Hi all--

We are going through the process of rationalizing our databases from SQL Server 2005 to 2012. In our development environment, however, we have many packages in SSIS 2005.

We plan on upgrading all of the packages from SSIS 2005 to SSIS 2012, but given the volume of packages necessary and certain standards we have to abide by when testing and deploying packages, it will take some time. (must be upgraded on local, then deployed to dev, then staging...)

My question is this: If I upgrade the engine and databases from SQL Server 2005 to SQL Server 2012, will my SSIS 2005 packages still execute properly with the SQL Server 2012 engine until we upgrade all of the SSIS packages from 2005 to 2012? Are there any caveats I should be aware of?

Thanks in advance!


There are some pretty large changes to the way SSIS is managed in 2012. First and foremost is that SSIS is no longer a separate server, but part of the sql service. Additionally, I believe (and check this) that they changed the configuration files. As such, my understanding has always been that different versions SSIS don't run on anything the SQL Server version they were built on, and this would be especially true going from 2005 to 2012.

However, the best thing to do is to try it. You never know. Might just depend upon the complexity of the package and the tasks that are being used.

Fraggle
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