.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
 
Sign In
Register
 
Win Surprise Gifts!!!
Congratulations!!!


Top 5 Contributors of the Month
david stephan

Home >> Articles >> DataBase >> Post New Resource Bookmark and Share   

 Subscribe to Articles

Options to execute a package in SSIS - SQL Server Integration Services (SSIS) - Part 6

Posted By:Karthikeyan Anbarasan       Posted Date: February 27, 2011    Points: 200    Category: DataBase    URL: http://www.dotnetspark.com  

In this article we will see on how to deploy a package once we are done with creating and building the package. Look around in to my previous articles on how to create, build and execute a package using SSIS at the below url's.
 

Introduction:

In this article we will see on how to deploy a package once we are done with creating and building the package. Look around in to my previous articles on how to create, build and execute a package using SSIS at the below url's.

Part 1

Basics of SSIS and Creating Package - SQL Server Integration Services (SSIS) - Part 1

Part 2

Transforming SQL Data to Excel Sheet - SQL Server Integration Services (SSIS) - Part 2

Part 3

Export Data using Wizard - SQL Server Integration Services (SSIS) - Part 3

Part 4


Import Data using Wizard - SQL Server Integration Services (SSIS) - Part 4

Part 5


Steps:

Once a package is created and build it successfully, we have 3 options to make a deployment. We will look into each approach with an example.

Approach 1: DTEXEC command line utility

SQL Server provides a command line utility (DTEXEC.EXE) that helps the developers to execute the SSIS package. It can be directly used from the command prompt by moving around to the folder where the package is available and executing making use of this EXE.

DTEXEC /? Provides the list of available options to execute the package from the command prompt as shown in the below screen


So to execute the package go to that folder where the package is available and provide the syntax as shown in the below screen

 

This is the result once we execute a package in SSIS Command line utility. This example shows an error that package is not executed properly and it has some errors which need to be fixed.

For more details on DTEXEC utility refer to the below msdn article

http://msdn.microsoft.com/en-us/library/ms162810%28SQL.90%29.aspx

Approach 2: SSIS Package Windows Application

This approach is straight forward a user interface option to execute the package. Microsoft has provided a user interface or we can say a tool kind of option to execute the SSIS packages. DTEXECUI.EXE is the User interface exe which performs the task of executing the package.

We can launch DTEXECUI.EXE by double clicking on the package itself directly (i.e. go to project folder and double click on *.dtsx file). It will open the graphical user interface as shown below.


As we can see there are many options available in order to execute the package based on our needs. If we want to follow the standard format then directly clicking on EXECUTE button at the bottom will do the task. We can navigate through each option and customize the package based on our needs.

You can have a look at the msdn article on DTEXECUI.EXE utility at the below url

http://msdn.microsoft.com/en-us/library/ms141707%28SQL.90%29.aspx

Approach 3: SQL Server Agent Scheduling

The last and the final approach to execute the SSIS packages are the SQL Server Integration services Job step type which helps to schedule the package and execute it based on our needs. This is one of the easiest approaches since we have the UI to schedule the package and execute it without any user interactions.

In order to do these approaches go to SQL Server Management Studio à Connect to the Database using the credentials à open object explorer and go to JOBS à Select New Job and fill the details based on our needs


 

Conclusion:

In this article we have seen the different options to execute the SSIS packages. We will look into the deployment options in the upcoming articles.


 Subscribe to Articles

     

Further Readings:

Responses

No response found. Be the first to respond this post

Post Comment

You must Sign In To post reply
Find More Articles on C#, ASP.Net, Vb.Net, SQL Server and more Here

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend