Deploying to the SSIS Catalog

RanjeetaNandaToday’s post is from Ranjeeta Nanda. Ranjeeta is an SDET (Software Development Engineer in Test) on SQL Server Integration Services team. She has been with the team since May 2004. Before joining Microsoft, she worked at Merkle Direct Marketing, Maryland. She has done her Masters in Computer Science from Georgia Tech, and B.Tech from IIT Delhi, India.



Once you have created and built a new or migrated project in Project Deployment Mode, you can use the new IS Deployment Wizard to deploy your project to the SSIS Catalog. To launch deployment Wizard, right click on the project in BIDS, and choose the Deploy option.


This will bring up the Deployment Wizard, that looks like this:


When starting from BIDS, the source page will be auto filled with the project location of the current project


For Destination, you could select a local or remote server, and specify a path on that server.


While selecting the destination, you could also create a new Folder on the required server


After that, you can review and deploy the Project to the destination server.


One can also start the deployment wizard by starting ISDeploymentWizard.exe from command prompt instead of starting it from BIDS. In that case, the source project could be specified either from file system as an .ispac file, or from existing SSIS Catalog project on local or remote server.


The Deployment Wizard makes it very convenient to deploy projects to an SSIS Catalog. Users can choose a .ispac file from file system, or project already deployed to a catalog as source, and deploy it to a destination SSIS catalog on remote or local server. In case you haven’t created an SSIS catalog on the local server yet, the deployment wizard might not be able to find a folder when Browse for the path. In that case, the user can create the catalog and re-click on the Browse button to see the catalog.

Comments (7)

  1. Nice post. But, it would be more helpful if you would have added the SSIS catalog at local server details also.

  2. Satadal says:

    Hi! Could you tell me how to implement the above programmatically as well? Thanks!

  3. Daniel says:

    It would be nice to output the summary report to the console when you execute the Deployment Wizard from command prompt

  4. Prakash says:

    @Satadal: You can refer Matt's blog on how to do it programmatically..…/10238256.aspx

  5. Praviin says:

    is it necessary that isdeploymentwizard.exe exists on target sqlserver machine to deploy .ispac file to integration services catalog of sql server 2012 ?

  6. No – you only need the deployment wizard on the client machine doing the deployment.

  7. Cody says:

    It would be nice to cover why we get errors with worthless messages. I cannot get mine to deploy successfully. So far, resources online are not very good.  

Skip to main content