In SQL 2014 SSISDB, how do I BACKUP an original SSIS Pkg, named PKG_A, residing in FOLDER_1 under SSISDB in the Integration Services Catalog

  • This will be for a contingency restore in the event the newly modified and deployed pkg w/ the same name, does not work. What is the best way to do this?

    - we're using SQL 2014 Enterprise

    - we have dozens of SSIS pkg's deployed to SSISDB in various folders (eg. PKG_A resides in FOLDER_1 under SSISDB in the Integration Services Catalog)

    - we're planning on deploying a modifed pkg, PKG_A, into FOLDER_1 under SSISDB on Integration Services Catalog which will overwrite the current PKG_A

    I realize the developers should be using a versioning tool like SOURCE SAFE to accommodate this but I want to know how to do this directly on the SQL Server. I'd like to RENAME the existing Pkg, PKG_A, as PKG_A_backup but there is no rename option when I right click on the actual pkg name.

    BT
  • Found a solution to backup my SSIS Pkg:

    - navigate to the SQL Server housing your package(s) requiring BACKUP

    - expand Integration Services Catalogs, SSISDB, and your Folder

    - right mouse click on your Project name

    - click EXPORT

    - provide a filename and click SAVE

    - this will gen an ISPAC file (a backup)

    - If you need to RESTORE, simply double click the ISPAC file you previously created and follow the instructions to DEPLOY

    - Note: this process will backup ALL packages in the Project AND restore ALL the packages to the Project; I realize Microsoft recommends this restore of ALL packages to ensure integrity across the project

    BT
  • If you right-click on a project in SSISDB, and select 'Versions' you will see a list of previously deployed project versions (the maximum number of versions displayed will depend on the 'Maximum Number of Versions Per Project' property of the catalog).

    It is possible to revert to any one of these versions without needing to go through the export/import process you have mentioned.

    The absence of evidence is not evidence of absence
    - Martin Rees
    The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
    - Phil Parkin

  • Great info on the VERSIONS option! Thank you.

    BT

Viewing 4 posts - 1 through 3 (of 3 total)

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