SSIS server migration – SSIS components connection managers not preserved

  • 1 September 2023
  • 0 replies
  • 30 views

Userlevel 2
Badge

If you are looking into migrating your SSIS workflows and packages to new servers running other SQL Server editions (e.g., say migrating from a server running SQL Server 2016 to one running 2019) and these packages use our SSIS components, it’s important to keep some things in mind: 

 

Before migrating the packages, you need to download and install whatever CData SSIS components you are using in the old server in the new server as well. During the installation, please make sure you check all the boxes for SQL Server editions (or at least all the ones involved in the process even though checking everything is the safest option): 

 

 

 

After installing the components, please import the package to the new server as it is (without doing any conversions or changing the target server version in the old server). Once the package is opened in the new server, please check if the component and its connection manager are correctly preserved there (if you have followed the installation instructions above, it should be). After verifying that, please go to the project properties and change the TargetServerVersion to the SQL Server edition desired in order to convert the packages and complete the migration.  

 

NOTE: It’s always good practice to have the same version of our SSIS components in the development server and production server (e.g., if you have our SSIS components for QuickBooks version 23.0.8634 in your development server, it’s important you have that same version installed in your production server as well). Keeping the versions synchronized is critical for avoiding potential errors.  


This topic has been closed for comments