Our IT department bought SQL Server 2012 Enterprise and VS 2013 Pro many years ago.
I realize that SQL Server 2012 Agent will not execute SSIS packages created in VS2013. So what are my options, if any?
Is there any way I can create SSIS packages in VS2013 that will run in SQL Server 2012?
Thanks.
The latest version of SSDT is free, and supports SSIS versions 2012 and later.
https://learn.microsoft.com/en-us/sql/ssdt/download-sql-server-data-tools-ssdt
Related
The question is can I use Visual Studio 2019 with the most current SSIS to create SSIS packages for SQL Server 2008? Or do I need to download an earlier version of Visual Studio?
I do not have access yet to execute on the server I am waiting for this and just doing some research to get tools ready in the mean time. So I have not tried anything yet.
You have to install SQL Server Data Tools (SSDT) for Visual Studio 2019.
This is the link
https://learn.microsoft.com/en-us/sql/ssdt/download-sql-server-data-tools-ssdt?redirectedfrom=MSDN&view=sql-server-ver15
Says that you can't.
Supported SQL versions
Integration Services packages SQL Server 2012 - SQL Server 2019
Unfortunately, SSIS 2008 is too old. Additionally, SQL Server 2008, and its SSIS, are out of support. I strongly suggest upgrading your SSIS to a later and supported version.
VS2019 supports SSIS development for the following SSIS versions:
2012
2014
2016
2017
2019
-- UPDATE --
can sql server2008 use ssis later than 2008? this is what i was trying
to establish
No, SQL Server version and SSIS version are one and the same.
-- UPDATE #2 --
BIDS (Business Intelligence Development Studio) can be found after installing the full version of SQL server 2008.
Check it out here: Creating a SSIS package in VS 2008
I have already existing system on Sql Server 2008, with SSIS. I don't have BIDS 2008 but Data Tools 2015. Is is possible to edit existing packages from 2008 in Data Tools 2015 and then run/deploy on 2008 server again? I know that I can't run newer packages on older server but what with packages created on 2008 but edited on 2015?
SSDT 2015 can create packages/projects for SSIS 2012, 2014 and 2016, based on your choice. You need to select target SSIS version.
Unfortunately, it cannot create packages for SSIS 2008. You need BIDS 2008 for that.
Packages for SSIS 2012 and higher cannot be run on SSIS server 2008.
I am developing a SSIS 2008 R2 package in Visual Studio 2015 using SQL Server Data Tools and i am getting the error listed below. Is these two truly not compatible or is there a setting I can change (or workaround)?
You cannot build a ssis package for sql server 2008 r2 with VS 2015.
According to this Microsoft Docs article you can build a sql server 2008 r2 ssis package with only visual studio 2008 (business intelligence developpment studio).
There are a lot of links saying that newer versions of visual studio cannot deploy SSIS 2008 packages correctly:
Can SQL Server Data Tools work with SQL Server 2008 SSIS?
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/bff5e145-1c63-4221-b2ba-009ea96a9e05/can-i-use-vs2012-to-create-and-deploy-ssis-for-sql2008r2?forum=sqlintegrationservices
https://www.sqlservercentral.com/Forums/Topic1560322-364-1.aspx
Can some one tell me whether the SSIS packages developed in Visual Studio 2012 or 2013 works in 2008r2 server or not ???
If yes, did any other software needs to be installed in the 2008r2 server?
Deployment is not any concern here. I just want to run the packages in 2008r2 server via sql agent job
Please help.
No. Backwards compatibility is not an option. A package built in 2014 will not run on 2012. A 2012 package will not run on 2008 and a 2008 package will not run on 2005.
However, forward compatibility does exist so a 2005 package will run on 2008. 2008 will run on 2012, 2012 on 2014.
While I don't think this is your scenario, if you have the 2012/2014 SSIS packages deployed to a 2012/2014 server, you could run them from the 2008 server's SQL Agent task. It'd just be a matter of scripting the catalog.create_execution and catalog.start_execution BOL
Having that SQL Script, add a job step task of SQL and point the context over to your 2012/2014 server.
MSDN at https://msdn.microsoft.com/en-us/library/mt204009.aspx contains an overview of all the supported VS/SQLServer version combinations.
Basically, for SQLServer2008R2 SSIS development you will need BIDS (from the SQLServer installation).
The VS2012/VS2013 tools support only SQLServer2012/2014 SSIS development.
For VS2015, the Februari preview release of the SSDT-BI tools is intended to support multi-targetting SSIS package development (but only SQLServer2012-2016, no 2008R2), see also in the comments at http://blogs.msdn.com/b/ssdt/archive/2015/12/16/sql-server-data-tools-preview-update-for-december-2015.aspx
Note there is also something called BIML which is able to generate SSIS packages for different versions of SQLServer (incl 2008R2) from the same source code, so you could possibly use VS2012/VS2013 with BIDSHelper and then as a last step maybe generate packages for SQLServer2008R2.
We have SQL Server & SSIS 2014 in our local environment, and most of SQL Server 2014 in our production environment, except for the SSIS, which is still 2008.
So we're creating SSIS packages locally which can't be deployed to production, because the SSIS packages are not backwards-compatible.
Is it possible to create the packages locally to target SSIS 2008? If so, how?
Just to note, the SSIS packages are defined in Visual Studio 2008, so I don't understand why they're dependent on SQL Server 2014.
The format of the SSIS packages has change from SSDT 2012 to 2013/2014. I was facing that situation recently before a Go Live. A colleague had developed SSIS packages in SSDT 2013 with SQL Server 2012 as the target environment for the deployment. While the development and execution from within SSDT 2013 with SQL Server 2012 is no problem, the package is not deployable within the SSIS catalog of SQL Server 2012. SSIS Packages are NOT downward compatible. ...at least with respect to the deployment in the SQL Server SSIS catalogue.
Open the dtsx file in the editor and check the value for "PackageFormatVersion". Possible values are:
VS 2013/2013 = 8
VS 2010/2012 = 6
Unfortunately, you cannot open SSIS packages with PackageFormatVersion=8 in SSDT 2012 or lower in order to downgrade a package. You could of course figure out, how the format has changed. I started to do this but gave up after a while. The best possible solution was to redevelop the package in SSDT 2012. Argh!
So, when developing SSIS packages you must take care of the target SQL Server version and then decide to choose the right SSDT version.