SSIS error when deploying from VS 2013 to SSISDB in SQL 2012

An SSIS package has been developed in SSDT-BI Microsoft Visual Studio Professional 2013 (freely available download). When we deploy the package to SSISDB in SQL Server 2012 RTM or SP1 (11.0.3153.0) and run it, it returns the following error, because the SSIS 2014 package format is not downgradable to SSIS 2012 version format.  “The package failed…

4

Script Component Recompile in SQL Server 2012 Integration Services (SSIS) to refresh metadata

In SQL Server releases 2005-2008 R2 there is a programmatic approach to be able to dynamically change dataflow columns and their data types in a dataflow task from the SSIS programmatic APIs, and have a Script Component still work magically (most of the time). In Microsoft Customer Service and Support we saw this from time…

1

VSTA setup and configuration troubles for SSIS 2008 and R2 installations

SSIS 2008 Uses VSTA 9.0 to edit Script Tasks and Script Task (in Control Flow) and Script Components (in Data flow tasks). VSTA stands for Visual Studio for Team Applications. It should look like this…  and when you click the “Edit Script…” button the Script editor VSTA windows opens when it works (which is most…

11

Visual Studio 2010 solution build process give a warning about indirect dependency on the .NET Framework assembly due to SSIS references

Here’s how I saw the problem… Install SQL Server 2005. Afterwards, Install SQL Server 2008. (Integration Services or Management tools features are enough usually) Install your favorite new tool Visual Studio 2010. Create or Open a solution for your C# or VB application. The Solution properties should target the “.Net Framework 3.5” to have this…

8