Developing packages in Visual studio 2012 to run against a 2008 r2 server.

Question

Developing packages in Visual studio 2012 to run against a 2008 r2 server.

peter 89731

SSC-Addicted

Points: 440
More actions
April 10, 2014 at 3:43 am

#290120

Hi,
The company I am working for has a 2008r2 server and packages developed using bids 2008. They are also using TFS, and because of some of the limitations with 2008 would like to upgrade packages and develop using 2012 data tools, targeting the 2008 ssis engine.
This seems problematic to me, both in terms of the upgrade path for the packages & developing using 2012 targetting the 2008 server.
If someone could provide some guidance on the advisability of doing this it would be very appreciated
Thanks
Peter

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply

Phil Parkin SSC Guru Points: 246695 More actions · Answer 1

peter 89731 (4/10/2014)
Hi,
The company I am working for has a 2008r2 server and packages developed using bids 2008. They are also using TFS, and because of some of the limitations with 2008 would like to upgrade packages and develop using 2012 data tools, targeting the 2008 ssis engine.
This seems problematic to me, both in terms of the upgrade path for the packages & developing using 2012 targetting the 2008 server.
If someone could provide some guidance on the advisability of doing this it would be very appreciated
Thanks
Peter

This is not going to work - packages developed in SSDT 2012 won't run on SSIS 2008, as far as I know.

If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

Koen Verbeeck SSC Guru Points: 259085 More actions · Answer 2

Phil Parkin (4/10/2014)
peter 89731 (4/10/2014)
Hi,
The company I am working for has a 2008r2 server and packages developed using bids 2008. They are also using TFS, and because of some of the limitations with 2008 would like to upgrade packages and develop using 2012 data tools, targeting the 2008 ssis engine.
This seems problematic to me, both in terms of the upgrade path for the packages & developing using 2012 targetting the 2008 server.
If someone could provide some guidance on the advisability of doing this it would be very appreciated
Thanks
Peter
This is not going to work - packages developed in SSDT 2012 won't run on SSIS 2008, as far as I know.

+1 You need the Visual Studio 2008 shell to develop SSIS 2008 packages.

You can use TFS in Visual Studio 2010 though to do the version control, if I'm not mistaken. I remember at a client we had VS 2008 for SSIS 2008R2, but also TFS in Visual Studio 2010.

Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP

peter 89731 SSC-Addicted Points: 440 More actions · Answer 3

Thanks, it's all pretty tricky I think. MS technet link http://technet.microsoft.com/en-us/library/bb522577.aspx says

You can load and run packages that were developed in SQL Server 2005 Integration Services (SSIS) and SQL Server 2008 Integration Services (SSIS), in the SQL Server 2012 version of SQL Server Data Tools (SSDT). When you add the package to an existing project, the package is permanently upgraded to the format that SQL Server 2012 Integration Services (SSIS) uses. When you open the package file in SQL Server Data Tools (SSDT), the package is temporarily upgraded to the format that SQL Server 2012 Integration Services (SSIS) uses. If you save the change to the package, the package is permanently upgraded. Once saved in the format that SQL Server 2012 Integration Services (SSIS) uses, packages can no longer be opened in the corresponding SQL Server 2005 or SQL Server 2008 version of Business Intelligence Development Studio, nor run by the corresponding SQL Server 2005 Integration Services (SSIS) or SQL Server 2008 Integration Services (SSIS) tools.

From this I understand that the package format is upgraded - does it mean that the package (& functionality contained) will not run against

2008 when using the dtexec command line ?.

Does it also mean that 2012 developed packages may contain features that are not supported by the 2008 dtexeccommand line and integration services service ?

Thanks - the client is not looking to upgrade the server.

Koen Verbeeck SSC Guru Points: 259085 More actions · Answer 4

The package will only be upgraded if you try to execute 2008 packages in a 2012 environment.

Since you don't have SQL Server 2012, you don't need to worry about this.

Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP

Phil Parkin SSC Guru Points: 246695 More actions · Answer 5

From this I understand that the package format is upgraded - does it mean that the package (& functionality contained) will not run against 2008 when using the dtexec command line ?.
Does it also mean that 2012 developed packages may contain features that are not supported by the 2008 dtexeccommand line and integration services service ?

Yes and yes.

If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

peter 89731 SSC-Addicted Points: 440 More actions · Answer 6

peter 89731

SSC-Addicted

Points: 440

April 11, 2014 at 3:02 am

#1705158

Thanks to all for the replies.

Lynn Pettis SSC Guru Points: 442467 More actions · Answer 7

One thing to note. If you had a server running SQL Server 2012 with SSIS also running, the SSIS packages running on that server can use SQL Server 2008 databases as both source and destination targets.