August 20, 2014
Hot Topics:
RSS RSS feed Download our iPhone app

Deploying and Configuring SQL Server Integration Services Packages Without the Wizard

  • October 2, 2008
  • By Dee Quang
  • Send Email »
  • More Articles »

Click OK again on the New Job window to create the job. The job should now be created and resemble Figure 10.

Figure 10: Directory after Job Creation

At the scheduled time, the job will process and complete. If the job completes without any errors, give yourself a pat on the back because you have successfully deployed an SSIS package via SSJA.

Ad-Hoc Execution

Whether packages are executed on a scheduled basis or not, packages can always be executed ad-hoc. Executing a package on an ad-hoc basis can be done in two methods. The first method is directly from the package in SQL Server's file system (SSFS). Find the package in SSFS and choose Run Package from the right-click menu to display the Execute Package Utility window. Click on the Execute button and the ad-hoc execution is complete. Figure 11 displays the Execute Package Utility window.



Click here for a larger image.

Figure 11: Execute Package Utility

The second method is by executing it through the job created for the package. Simply right-click on the job and choose Start Job. That is all that is needed to execute the packages ad-hoc.

Configuring Packages

Packages can be configured in a multitude of ways. They also can be configured individually or globally. This article so far has only used the default package configuration to individually configure and execute the package. In addition to the default package configuration method, this section will describe two other methods to configure the package.

Default Package Configuration

The default package configuration method uses the package's connection manager's OLE DB connection transformation to configure the server credentials. This method is used to configure the packages individually. As seen in Figure 12, the server name and server credential can be entered in the Connection Manager window.

Figure 12: Connection Manager Window

When a package is schedule by the SQL Server Job Agent or executed ad-hoc and configurations are not specified, the default package configuration will be used.





Page 4 of 6



Comment and Contribute

 


(Maximum characters: 1200). You have characters left.

 

 


Sitemap | Contact Us

Rocket Fuel