Share via

20,000 foot view of my ssis options as we upgrade from sql 2014 to 2019

db042190 1,521 Reputation points
2023-04-18T11:24:17.09+00:00

hi, its been so long since i got into the details of a project like this that some of these questions will undoubtedly seem dumb. i'm sure we will upgrade vs too from 2013 to 2017 or 2019. currently out pkgs are stored in vs and dbo.sysssispackages i believe on msdb.

  1. i kind of remember how cool and powerful the catalog is but are our target migration choices (no matter how silly) to go to... a. file system b. maybe our new server's sysssispackages c. the catalog
  2. if we go to the catalog how (what steps high level) do most people migrate their pkgs? forget about configs vs params for the moment, how does the typical pkg get over to the new server's ssisdb and what is the biggest change in sql agent jobs where they reference the pkgs that they run?
SQL Server Integration Services
SQL Server Integration Services
A Microsoft platform for building enterprise-level data integration and data transformations solutions.
2,705 questions
Accepted answer
  1. ZoeHui-MSFT 41,496 Reputation points
    2023-04-19T06:33:40.6466667+00:00

    Hi @db042190,

    Upgrade SSIS2014 to SSIS2019, you may refer the official documentation.

    You may also refer to Upgrade and Migrate SSIS Catalog and SSISDB.

    Regards，

    Zoe Hui

    If the answer is helpful, please click "Accept Answer" and upvote it.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Yitzhak Khabinsky 26,586 Reputation points
    2023-04-18T12:43:06.7433333+00:00

    Hi @db042190,

    You should definitely go with the SSIS Catalog. Please watch this video: https://www.youtube.com/watch?v=x4I1WOaRm94

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.