In my last post I talked about creating a Deployment manifest, so in keeping with the SSIS package deployment them I thought I would cover another method of deploying SSIS Packages. This method requires you to log into the SSIS server itself. Lets walk through the steps together.
Open Management Studio and change the option to Integration Services in the Server Type box:
Next you need to set the Server Name property, I’m using my local machine, but yours might be the same as your SQL Server or another server altogether. Once you have the Server Type and Server Name set then connect to the server.
On the left hand side the object explorer should be visible. You should see the name of your server and two folders underneath it:
- Running Packages
- Stored Packages
It is the Stored Packages folder that we are concerned with. If you expand the folder you should see two subfolders
- MSDB
- File System
These folders indicate where you want to import the packages too, either in the file system or into MSDB. Right click on the folder or your choice and select “Import Package” (I’m using the file system in this example)
From the new menu screen you must first select where the package you want to import is located, either SQL Server, File System or SSIS Package Store.
If you are using SQL Server you must next tell it the server name and the type of authentication to use (and username and password if you use SQL Server Authentication), then specify the package in SQL Server. If you are using the file system just specify the package path. You can also set the package protection level here as well.
Click ok and the package has now been imported. Please note that this will only bring in the package, so if you have any package configurations you must deploy those separately. Next time we’ll cover deploying a package from BIDS using the SaveCopyofPackageAs option.
No comments:
Post a Comment