Integration Services in VS 2019 Version Mismatch with the one in SQL server 2019

Ashley Gobio 1 Reputation point
2020-12-28T17:54:58.36+00:00

I am SSIS in C# developer. We have an application invoking SSIS packages in C# prgram. We recently upgraded the SSIS packages using VS 2019, so the Integration Services installed with VS 2019 is version 1.3. We are planning to move the program into production Environment in which VS 2019 is not allowed to install. So we installed integration services using 2019 SQL server installer. It doesn't work since the Integration Services included SQL server 2019 is version 1.5. The program can't find the right reference and throw error msg saying can't find Integration Services.

Is there a way to build SSIS packages that can reference to multiple versions of Integration Services? Or is there a way to install the Integration Services 1.3 without install vs 2019?

This is urget! Please help!

Visual Studio
Visual Studio
A family of Microsoft suites of integrated development tools for building applications for Windows, the web and mobile devices.
4,600 questions
SQL Server Integration Services
SQL Server Integration Services
A Microsoft platform for building enterprise-level data integration and data transformations solutions.
2,451 questions

6 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Yitzhak Khabinsky 24,946 Reputation points
    2020-12-28T18:35:40.887+00:00

    It is not exactly clear what is going on based on the overall question.

    In any case, I will try to answer on your direct questions:

    1. Is there a way to build SSIS packages that can reference to multiple versions of Integration Services?
      No, SSIS project and all its packages are targeting one particular SSIS run-time version. It is specified in the SSIS project properties via the TargetServerVersion setting.
    2. Or is there a way to install the Integration Services 1.3 without install vs 2019?
      It could be done by using SQL Server installer, but will require the SQL Server instance to be installed too. So it is not what you need. You could try to copy needed SSIS assemblies manually to a dev. machine where VS2019 installed.
    0 comments
  2. Ashley Gobio 1 Reputation point
    2020-12-28T19:23:23.837+00:00

    Hi,Yitzhak
    Thank you for your prompt response.

    If I go with the option 2, which is install sql server on my dev machine, how I can make the SSIS package refer to this version of the integration services? By using the TargetServerVersion setting?

    What about installing vs 2019 on a computer and then remove visual studio? Can we keep the Integration Services in this case? Or Once the visual studio 2019 is removed, Integration services will be gone too?

    0 comments
  3. Ashley Gobio 1 Reputation point
    2020-12-28T19:32:12.733+00:00

    Hi, Yitzhak
    I took a look at the setting TargetServerVersion. It seems pointing to the SQL server version. The SSIS packages connect to a SQL server on version SQL sever 2014. The Integration Services reference is in 2019. Should TargetServerVersion be SQL 2014 in this case?

    Thanks,

  4. Monalv-MSFT 5,891 Reputation points
    2020-12-29T08:29:27.867+00:00

    Hi anonymous userGobio-0248 ,

    The SSIS packages connect to a SQL server on version SQL sever 2014. The Integration Services reference is in 2019. Should TargetServerVersion be SQL 2014 in this case?

    In VS 2019 or in SQL Server Data Tools (SSDT), we can create, maintain, and run packages that target SQL Server 2019,SQL Server 2017, SQL Server 2016, SQL Server 2014, or SQL Server 2012.

    TargetServerVersion specifies version for saving, deployment, execute and debug the package in SSDTBI.
    51807-targetserverversion.png

    This means the following two situations：

    Situation1: (Extract projects or packages from TargetServer)
    We have created a ssis project in SQL Server 2019, but now we want to open and run the packages that were created in SQL Server 2014.
    We should set the TargetServerVersion as SQL Server 2014 in SQL Server 2019.
    If we do not set the TargetServerVersion, it may appear error or it will upgrade the ssis packages.

    Situation2:(Deploy projects or packages into TargetServer)
    We have created a ssis project in SQL Server 2019, but we want to deploy it to SSISDB Catalog in SQL Server 2014.
    We also should set the TargetServerVersion as SQL Server 2014 in SQL Server 2019.

    Best Regards,
    Mona

    ----------

    If the answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
    Hot issues in November--What can I do if my transaction log is full?
    Hot issues in November--How to convert Profiler trace into a SQL Server table?

    0 comments
  5. Ashley Gobio 1 Reputation point
    2020-12-30T16:08:41.06+00:00

    Thank you for your helps. We are still investigating. It seems like SQL server 2019 is not good candidate for us to deploy SSIS packages.

    What is the version of Integration Services in SQL server 2014? How come I can't find the SQL server 2014 download link from Microsoft download center?