Migrate the SSIS Catalog in Just a Few Clicks

  • Interesting, I had no idea that this tool even existed!

    Does it also migrate the run history? (That is, the information displayed on the All Executions report.) If migrating from one instance to another, it may be desirable to keep this history.

    If the answer to your question can be found with a brief Google search, please perform the search yourself, rather than expecting one of the SSC members to do it for you.
    See https://www.sqlservercentral.com/articles/forum-etiquette-how-to-post-datacode-on-a-forum-to-get-the-best-help/ for details of how to post T-SQL code-related questions.

  • Hi Phil,

    Glad to know that you found this plugin interesting.

    This tool is designed to migrate full or part of SSIDDB catalog artifacts (SSIS projects & environments). Also, the target Integration Services Catalog can be a new or already existing environment.

    In our project, we use this tool to frequently promote SSIS project builds from  DEV ->TEST and further environments.

    Hence, it would be a bit challenging to migrate the historical execution log. Having said that, it might make sense in case the target SSISDB is fresh and we are planning to migrate everything from the source. I will definitely give it a thought.

    Thank you!

    Regards,

    Kunal

  • Kunal Rathi wrote:

    In our project, we use this tool to frequently promote SSIS project builds from  DEV ->TEST and further environments.

    Hence, it would be a bit challenging to migrate the historical execution log. Having said that, it might make sense in case the target SSISDB is fresh and we are planning to migrate everything from the source. I will definitely give it a thought.

    Thank you!

    Regards,

    Kunal

    May I ask why you would use this tool in preference to an automated deployment from source control when moving packages between environments?

    Being able to move the history would be a useful (optional) selection, in the case where an existing SSISDB is being moved from one instance to another, but within the same environment (eg, non-in-place upgrade of Prod SQL Server version). That's because some companies will be using the data to track historical run statistics, looking for trends and anomalies.

    If the answer to your question can be found with a brief Google search, please perform the search yourself, rather than expecting one of the SSC members to do it for you.
    See https://www.sqlservercentral.com/articles/forum-etiquette-how-to-post-datacode-on-a-forum-to-get-the-best-help/ for details of how to post T-SQL code-related questions.

  • At our place, we are always creating and deploying new solutions from qa to prod and this is always a very time-consuming job for my junior DBA's. I did have a stored prod I found online that allowed me to script out the variable names and re-execute them in prod, but it failed to do any of the re-mappings we needed. Also, my junior DBA's found it confusing and often didn't leverage it. I never heard of this tool before. This will be much easier for my team to follow. This tool is an absolute game-changer for my team. Thanks a lot for sharing this.

  • Follow all the latest updates to this tool at https://azureops.org/articles/ssis-catalog-migration-wizard/

     

    • This reply was modified 5 months ago by  Kunal Rathi.
    • This reply was modified 4 months, 2 weeks ago by  Kunal Rathi.
  • Comments posted to this topic are about the item Migrate the SSIS Catalog in Just a Few Clicks

Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply