This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(51.2, 55.00000000000001%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Will a simple copy from one sqlserver to another sqlserver complete the process?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(67.2, 1%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETP%3C/text%3E%3C/svg%3E)
You are better off redeploying the SSIS code, rather than trying to "copy" them from one server to another.
How do you I redeploy SSIS code?
Your SSIS packages should be stored in source control You can redeploy them from Visual Studio.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 78%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECZ%3C/text%3E%3C/svg%3E)
Hi,
Please refer to the following posts about upgrading SSIS packages.
https://stackoverflow.com/questions/48750558/move-ssis-packages-from-sql-server-2008-r2-to-sql-server-2016/48754165
https://social.msdn.microsoft.com/Forums/SqlServer/en-US/7bd89ccc-1f9b-4be8-892f-6fc1c08cf5da/move-ssis-package-from-one-server-with-sql-2008-r2-to-another-server-with-sql-2016?forum=sqlintegrationservices
@Cris Zhan-MSFT thank you for the response, I am new to SSIS package migration. I have exported the package to the destination server. Tried to launch SSIS on the destination server. Got the error Connecting to the Integration Services service on the computer "servername" failed with the following error: Connecting to the Integration Service failed: The specified service does not exist as an installed service. I have 18.1 and 17.9 Microsoft Sqlserver Management Studio installed. But could not launch SSIS on sqlserver 2016. Is the correct process I am performing to migrate SSIS from target 2008R2 to destination(2016). Do you have more easy to follow instructions?
Have you checked the SQL Server configuration manager to make sure the SSIS service was running.
For the legacy Integration Services service running on an instance of SQL Server 2016, you may need to use the version of SSMS released for SQL Server 2016.
SSMS 16.5.3
https://learn.microsoft.com/en-us/sql/ssms/release-notes-ssms?view=sql-server-2017#1653
@Cris Zhan-MSFT Thank you so much, sure enough it was the version of the SSMS that was causing issues to connect to SSIS. I would like to leave this thread open for few days until the packages are migrated from 2008r2 to 2016.
Completed exporting the packages from 2008r2 to 2016, Tried upgrading the package but not all steps were successful. Might have permission issue that need to be resolved.
Also what version of free Visual Studio should I download in SQL server 2016. In sqlserver 2008R2 we had visual studio 2008 Shell. Please send me the link to download visual studio for SQL Server 2016. I have installed Visual Studio 2017, but when I try to open the package, it stated incompatible and The application is not installed.
Hello,
There are multiple ways to upgrade your old Integration Services Packages, check this doc:
https://learn.microsoft.com/en-us/sql/integration-services/install-windows/upgrade-integration-services-packages?view=sql-server-ver15
running SSIS Package Upgrade Wizard from SSMS or SSDT
https://learn.microsoft.com/en-us/sql/integration-services/install-windows/upgrade-integration-services-packages-using-the-ssis-package-upgrade-wizard?view=sql-server-ver15
@Cris Zhan-MSFT what version of visual studio should I install on Sql server 2016 so that the user can modify and execute the package.
Hello,
> I have installed Visual Studio 2017, but when I try to open the package, it stated incompatible and The application is not installed.
So you cannot open the 2008 R2 Integration Services project or packages with SSDT for Visual Studio 2017?
@CathyJi-MSFT , downloaded VS https://visualstudio.microsoft.com/vs/older-downloads/, Microsoft Visual Studio Community 2017, version 15.9.36, when opened the solution X(incompatible),
Is Visual Studio 2017 not compatible with SQLServer 2016 Microsoft SQL Server 2016 (SP2) (KB4052908) - 13.0.5026.0 (X64) Mar 18 2018 09:11:49 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows Server 2016 Standard 10.0 <X64> (Build 14393: ) (Hypervisor)
Open the SSIS package in Visual Studio 2017 but so not see the control flow as in 2008R2 version. dtsx opens the xml file where <DTS:Property DTS:Name="PackageFormatVersion">3</DTS:Property> Do I need to convert it to a different version? What is the process of conversion?
Hi,
Please download and use the SSDT for Visual Studio 2017.
https://learn.microsoft.com/en-us/sql/ssdt/download-sql-server-data-tools-ssdt?view=sql-server-ver15#ssdt-for-vs-2017-standalone-installer