The Business Intelligence Blog

January 14, 2010

Deploying Integration Services Packages manually

Filed under: SSIS — Tags: , , , — Shahfaisal @ 9:00 am

Since Integration Services packages are merely XML files, you can copy them to the destination server manually or by using a script. When using this method, you will have to explicitly copy the dependency files as well on the destination server. Once the packages are copied to the destination server, you can schedule to execute them using SQL agent or any other utility.

Securing packages:
Since in this method you will be copying the Integration Services packages on to a File System, the packages can be encrypted using the Package Protection Level property as well as by controlling access to the package and the dependent files(configuration files, checkpoint files, log files etc) by using folder/file permissions at the operating system level.

Please note that the Package Protection Level does NOT protect files that are stored outside the Integration Services package. For example configuration files, checkpoint files, log files will not be protected by the package protection level, so you will have to secure them using some other means such as folder/file permissions at the operating system level.

Advertisements

1 Comment »

  1. […] 3. Manually deploying the package to the File System. […]

    Pingback by Deploying Integration Services Packages « My Blog — January 14, 2010 @ 9:01 am


RSS feed for comments on this post. TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Create a free website or blog at WordPress.com.

%d bloggers like this: