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.
Related
I'm trying to use SSIS of SQL Server 2014, I already had SQL Server so I've followed some tutorials of how to add the SSIS functionality. I downloaded the setup of SQL Server but SSIS is missing when I look for it.
I read on a previous post that it's because I'm downloading SQL Server express
https://www.microsoft.com/en-us/download/details.aspx?id=42299 and that version doesn't have that feature.
But I've seen videos where they have the same link and to them do appear the SSIS when they're doing the same procedure.
My question: what can I do to use SSIS of SQL Server because I have Windows 7 and other versions as SQL Server 2016, 2017 need Windows 8 or newer, but I don't want to install them.
You can download SQL Server Developer Edition, if you are just planning to use it for development purposes. It is having SSIS coming with it.
SQL Server Developer Edition 2014 supports Windows 7. You can see more details here
The SQL Server Developer Edition 2014 download instructions are available in the Stackoverflow post
You need to install Sql Server Developer Tools-BI (SSDT-BI) to work on Integration Services Project. You can download SSDT from here. Choose the one corresponding to SQL Server 2014.
I have a bunch of SSIS packages created in SQL Server 2012. As new SQL Server versions come out, we have to provide a these packages in a format for SQL Server 2014, 2016 (every time for a new SQL Server version).
To do this, we manually upgrade packages, and store them in our repository for each SQL Server version. Obviously, this isn't great as the only difference is the SQL Server version they are compatible with.
Currently, there is an Integration Services project behind these in Visual Studio 2017, and via the IDE, you can upgrade all the packages via the flick of a switch.
Ideally, I'd like my Jenkins CI to do this conversion for me to each SQL Server version and make the packages available in each SQL Server version. Can this be done? I don't want to store every version package in my repo for distribution really...
TIA.
I am running into a problem as outlined in this artice: Execution error while validating script component. I am using Visual Studio 2015 to create SSIS packages and also upgrade old 2008 packages to be supported on SQL Server 2016. First, Visual Studio was able to upgrade the packages and I can run them successfully from within VS2015, but not as a job on SQL Server 2016 using SSMS 2017.
The article says to use the same version of SSMS as your SQL Server and your Integration Services package version. Is this indeed the case even with SQL Server 2016, Integration Services deployment set to 2016, and SSMS 2017?
I get the error that says the script task is corrupted. I have tried it using deployment versions 2016 AND 2017. Here is the error for deployment version 2017 (similar errors in 2016):
Note that I even went so far as to completely rewrite new script tasks using the same code as the old ones. I did have to add a reference to some .NET stuff for Directory Services though. But it compiled after I made that change.
Any help is appreciated!
Well I wasn't able to get SSMS 2016 on the server due to delay in change request but I did do a deployment from within Visual Studio to the destination server and all is well. I found that here: Deploying SSIS Package to SQL Server 2016
I didn't install anything on my destination server though. I just deployed from directly within Visual Studio on its server. Some of my scripts had to be rewritten but it wasn't much of a headache.
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.
I am trying to save an SSIS package on a sql server running 2005. The issue I have is that I am using SQL Server Management Studio 2008 on my local machine to do this and it won't let me save the package in on the server because its not compatible with 2008.
Is their some kind of compatibility option in management studio that I don't know about?
The short answer is no: the 2005 and 2008 package formats are different, and 2008 packages can't be downgraded to 2005.
The best solution is probably just to install the 2005 tools alongside the 2008 ones and use them for designing your packages.