In this article, we will show you the step-by-step approach to deploying the SSIS package using SQL Server or Integration Services Catalog.
Deploy SSIS Package Using SQL Server; let me open the Management Studio. Next, please navigate to Integration Services Catalog -> SSISDB -> Deploying Projects -> Projects under the Object Explorer will show the newly deployed project.
How to Deploy SSIS Package Using SQL Server
To Deploy Package Using SQL Server, right-click on the Projects folder, and select the below-marked option.
Once you select the option, a new Integration Services Deployment Wizard window will open. It is an introduction page, and by clicking the Do not Show this Page Again, you can avoid this page.
Select Source: This page is used to specify the source path
- Project deployment file: Please specify the system path where the project file is located.
From the below screenshot, you can see that we are selecting the Event handling project file of type .ispac
Please cross-check all the options.
- Server Name: Please specify the instance. Here it will automatically select the default instance localhost because we started this wizard using this instance. But you can change it to the Named instance that you use to access databases.
- Path: You have to specify the Integration Service catalog path. If you haven’t created a catalog, please refer to Create Catalog article to understand the steps.
Here, we are selecting the named instance PRASAD.
Please cross-check all the information, and if you find anything wrong, use the Previous button to go back.
The results page will show the result. As you can see, we have successfully deployed the SSIS package to SQL Server.
Let me open the Management Studio, and please navigate to Integration Services Catalog -> SSISDB -> Deploying Projects -> Projects under the Object Explorer will show the newly deployed project.
You can Execute the package by right-clicking the Event Handlers in SSIS Package and selecting Execute.. option from the context menu.
TIP: We already explained the Execution process in our previous article. So, please refer to the Using BIDS article to understand those steps.