I have SQL Server 2014, 2012, 2008R2, and 2008 installed on the same machine. The Integration Service Catalogs/SSDB are associated with SQL Server 2012.
I have developed some packages in BIDS 2008. When I use the "old" package deployment method to generate the SSISDeploymentManifest file, and choose the SQL Server 2008 instance (i.e., (local)\SQL2008 in my case) to store the packages, I get the message:
Storing or modifying packages in SQL Server requires the SSIS runtime and database to be the same version. Storing packages in earlier versions is not supported.
When I connect to Integration Services using SSMS, the packages are not deployed under MSDB.
Reason:
Although I developed the packages in BIDS 2008, but there is only one instance of SSIS per machine. The SSIS runtime on my machine is associated with SQL Server 2012.
Solution:
On the target server, use (local)\SQL2012, not (local)\SQL2008, not (local) - the default instance for SQL Server 2014. Now the SSIS runtime and the storing database are the same version, both are SQL Server 2012.
Now I can see the packages developed in BIDS 2008 are deployment to the MSDB of SQL Server 2012. All of the them are aligned.
Upgrading the package is not required in this approach. The version of the package is still 3, meaning BIDS 2008 (You open the package with Notepad or XML, and then search for PackageFormat. Version 2 is 2005, 3 is 2008, 6 is 2012, 8 is 2014).
So the lesson learned: using the single and compatible of SQL Server and Visual Studio only on a machine. The design of the single instance of SSIS per machine sometimes makes you "Ouch!'
