January 25, 2013 at 8:00 am
We have a couple dozen SSIS packages created in Visual Studio 2005. They run against numerous SQL2005 instances. We are essentially a mainframe shop; therefore most of these SSIS packages are started from a .bat called from the scheduling system used by our mainframe (because there are dependencies that certain steps need to complete successfully on the mainframe before the SSIS packages kicked off and vice versa). This scheduling system runs a pc where we have the SSIS 2005 components installed. We are getting ready to upgrade our instances to SQL2012 and we need to convert our SSIS packages too since they were still created in Visual Studio 2005.
Question: if we load Visual Studio 2012 (and remove the Visual Studio 2005 components) on the pc that has the scheduling software, will it still be able to run the SSIS packages created in 2005? I really would like to change, test and promote the SSIS packages in chunks since many of them are completely unrelated to each other.
Thanks for your help!
January 26, 2013 at 7:00 am
sford-721104 (1/25/2013)
We have a couple dozen SSIS packages created in Visual Studio 2005. They run against numerous SQL2005 instances. We are essentially a mainframe shop; therefore most of these SSIS packages are started from a .bat called from the scheduling system used by our mainframe (because there are dependencies that certain steps need to complete successfully on the mainframe before the SSIS packages kicked off and vice versa). This scheduling system runs a pc where we have the SSIS 2005 components installed. We are getting ready to upgrade our instances to SQL2012 and we need to convert our SSIS packages too since they were still created in Visual Studio 2005.Question: if we load Visual Studio 2012 (and remove the Visual Studio 2005 components) on the pc that has the scheduling software, will it still be able to run the SSIS packages created in 2005? I really would like to change, test and promote the SSIS packages in chunks since many of them are completely unrelated to each other.
Thanks for your help!
You can run multiple versions of VS side-by-side. I would not remove the 2005 components until all packages have been upgraded. By the way, VS 2012 does not support SSIS development at the moment. VS 2010 (shell underlying SQL Server Data Tools, SSDT) is actually the SSIS 2012 development IDE at the moment.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply