Systems Engineering and RDBMS

  • Click Here for Decipher's Homepage

  • Categories

  • Questions?

    Please send your wish list of things that you would like us to write about or if you have suggestions to help improve this blog site. You can send all questions/suggestions to: Blog Support
  • Archives

  • Blog Stats


Deploying SSIS Packages in SQL Server 2005

Posted by decipherinfosys on September 16, 2008

In our last post on SSIS, we dealt with the creation of Integration Services Configurations and how the configuration files help us in altering the package properties at run time. As explained in our previous posts, the SSIS package is created in the Business Intelligence Development Studio (BIDS) and saved on the client. In this post we will discuss the deployment of the SSIS packages we created onto the SQL Server.

Deploying the SSIS Package to the Destination Server:

There are three steps involved in the deployment of the SSIS Package to the target server.

1. Creation of the Package Deployment Utility.
2. Copying of the Deployment Folder to the Target Server.
3. Running the Package Installation Wizard to deploy the package onto the target server.

1. Creation of the Package Deployment Utility:

Deployment utility is a folder which contains the files to be deployed to the target server. The Deployment utility is created on the client machine where the SSIS Package resides. In this post we will deploy the package which we made use of in our last post for which we created the configurations. I am placing the project folder in C:\SSIS\Packages location on the hard drive. The project name as well as the Folder Name is TextFileImport. Open up the solution for this Project. The figure below shows the SSIS Package:

We can include the miscellaneous files like the Read Me File or the Sample File for the Text File Import in the Miscellaneous folder of the Solution. For demo purposes let us include the text file for deployment. To do this, right click on the Solution and in the pop up menu move the mouse over Add option and click the Existing Item. The image shown below depicts this:

This will open up the Add Existing Item box. Browse to the text file location and click on Add button. The image below shows this:

To create the deployment utility and build the project we should modify the package properties. To do this right clicks on the project and in the pop up menu click Properties. The image below shows how to open up the Package Properties:

The property pop up for the SSIS package is as shown in the image below:

In order to create the deployment utility, click on the Deployment Utility option in this window. The following image shows the Deployment Utility Properties which should be modified to create the deployment utility:

To create the deployment utility change the CreateDeploymentUtility option to true. When we build this package the deployment utility is created in the location pointed by the DeploymentOutputPath. This path can be changed to our liking. For the purpose of this demo, we are going to leave it as the default. The default path is the bin\Deployment folder in the Project Folder. In our case it is C:\SSIS\Packages\TextFileImport\TextFileImport\bin. Click Apply and then Ok to return to the BIDS. To build the project right click on the Solution and click build on the pop up menu. The image shown below depicts this:

After building the solution, the deployment utility is created in the default location if the build is completed successfully. Navigate to the deployment folder, C:\SSIS\Packages\TextFileImport\TextFileImport\bin\Deployment in our case and we will find the deployment files i.e. the integration services deployment manifest file, the configuration files, and the sample text file for import.

2. Copying of the Deployment Folder to the Target Server:

After creating the deployment utility, next step is to copy the deployment folder to the target server. For our demo purpose we are going to deploy the package in our local machine itself. Hence, I am going to launch the Package Installation Wizard from the deployment folder location itself.
3. Running the Package Installation Wizard:

Navigate to the deployment utility folder created by building the SSIS Project. Launch the Package Installing Wizard by double clicking on the Deployment Manifest File. The image below shows the Welcome Page of the Package Installation Wizard:

We have option to bypass this page next time we run this wizard by clicking on the little check box near the Do not Show this starting page again. For this demo we will leave this box unchecked and click on Next. The next page shows the options available for us to deploy the package. The image shown below depicts this:

There are two options available for us to deploy the SSIS Packages.

a) File System Deployment:

As the name suggests, this option allows us to deploy the SSIS Project to the File System i.e. a physical location on the hard disk on the target server. If this option is chosen, we have to back up the SSIS Packages manually every night for any disaster recovery.

b) Sql Server Deployment:
This option allows us to deploy the SSIS project to the SQL Server i.e. on the MSDB database. Since the msdb is usually backed up every night, this method of deployment saves us some extra work of backing up the SSIS Packages manually if deployed using the file system.

For this demo purpose let us select the Sql Server Deployment Option and Click next. In the next page we have to specify the target server information. For our demo purpose let us install this package on our local server. The image below shows the Target Sql Server Page of the Package Installation Wizard:

Specify the server information i.e. the local host and the authentication used to log into the server and click next. The next page asks us to specify the package installation folder. By default the folder is C:\Program Files\Microsoft SQL Server\90\DTS\Packages\<Project Folder Name>. In our case it is, C:\Program Files\Microsoft SQL Server\90\DTS\Packages\TextFileImport.

If you want to change the installation folder you are welcome to do so by clicking browse and selecting the installation folder. For this demo, let us leave this as default and click next:

Click next and the Wizard shows the Confirmation Page. Clicking on Next takes us to the Package Configuration Page. The server by default selects the Configuration File. The Configuration File can be found in the installation folder after the package is deployed on the server. The image below shows the Package Configurations Page:

Clicking on next takes us to the summary page. Review the Package Summary and click on the Finish button to complete the Installation.

Viewing the deployed SSIS Package on the Server:

To view the deployed package, log in into the Integration Services Engine using the Sql Server Management Studio. To do so, on the Server Connection dialogue, select the Integration Services as the Server Type, the Target Server Name and the required authentication type and click connect. In our case the target server is our local machine.

In the Object Explorer, navigate to the Stored Package folder. Since we stored the package on the SQL Server (MSDB), we can find our package in the MSDB Folder. Alternatively we can see that there is an entry in the sysdtspackages90 table in the msdb database for our SSIS Package. The image below shows this:

Running the SSIS Package from the SQL Server:

The SSIS Package can be run manually from the Server by right clicking on the Package and clicking on Run option in the Pop up menu. This opens up the Execute Package Utility. The image below shows the Execute Package Utility:

In this utility we can optionally specify the Configuration Files in the Configuration Page. The various options in this utility are left as an exercise for the reader. Alternatively the Execute Package utility can be invoked from the command prompt by typing the command dtexecui:

Type the command dtexecui at the command prompt and hit the enter key. This will pop up the Execute Package Utility as shown in the image below:

The SSIS Package can be run by selecting the appropriate values in the related text boxes.
In our case, since we deployed the package to the SQL Server select the SQL Server option in the Package Source text box and specify the target server name. Then the text box for Package gets enabled and we can choose the package to execute.

We can also execute the SSIS package from the command prompt or using the xp_cmdshell extended stored procedure by using the dtexec command line utility. This is the command line for executing the SSIS Packages rather than using the GUI for executing them. You can read more on the dtexec utility in BOL or at MSDN over here.

To Sum Up

In this post, we discussed the various steps involved in deploying the SSIS Package on the Server. We also went ahead and deployed one of our packages created as a part of this SSIS series on the SQL Server in the MSDB system database. We also saw the various methods to execute the SSIS Package including the command line utility dtexec. In the next post in the series, we will look into the scheduling of this SSIS Package to run as a job in SSMS.

43 Responses to “Deploying SSIS Packages in SQL Server 2005”

  1. […] Deploying SSIS Packages in SQL Server 2005 […]

  2. Ravi said

    This is a detailed one helped me alotto deploy.

  3. nonojojo said

    I am having a problem when I change a configuration value in the wizard when I try to execute the package from the management studio and click on run package when I choose the configurations tab my configuration file is not there and when I run the package the changes to the configuration file have not been implemented… isnt the purpose of the configuration step of the wizard to modify the configurations and associate it whith the package … can someone tell me what I am missing

  4. Craig Davis said

    Well done…this is very helpful in getting started with SSIS. Thank you for taking the time to add screenshots as well!


  5. Lian said

    Thank you so much, this very detail and helpful article helped to deploy the package

  6. Ady said

    Thank you so much, this is helpful. But i still can’t execute package using xp_cmdshell. Is there any helful detail article about this?

  7. srinivas said

    I have followed step by step as mentioned in your article. Everything went through. But, when i execute the package, it is failing with the error message “CANNOT ACQUIRE CONNECTION FROM CONNECTION MANAGER. THE ACUIRECONNECTION METHOD CALL TO THE CONNECTION MANAGER …… FAILED WITH THE ERROR CODE 0xC0202009”.
    what could have went wrong!!. Please help.

    Looking forward..


    • nageswararao said

      hai srinivas,
      i think in the dataflow ..some problem in connection managers like path and wrong table name like that..
      verify that and try once again …
      u can get it over …


  8. Ramireddy said


  9. srinath said


    It saved my day.

  10. Yurk said

    Muchas pero muchisimas gracias, si no fuera por tu post no se que hubiera hecho… lo repito una vez mas… Idolo!!!
    Saludos desde Perú … (2)

  11. Yaman Gupta said

    hi ,

    Thanks a Lot .

    one Problem when i am select option in ( Package installation wizard )
    OPTION is :-
    . Sql Server deployement ( Not File system deployment ) then my package not saved properly .

    pls suggest me .

    • nageswararao said

      it will locate the folder u specified and one thing u do ..
      go to sql server and connect as integration service role..
      select MSDB database in object explore..
      then it opens the project file..
      right click on that and run the project..then it will run..

      try this it will work …


  12. Karan Sharma said

    I tried doing following and received error

    I am tryin to extract data from a SQL 2000(other machine) to SQL 2005(my machine)
    I made one SSIS package on SQL 2005. package works fine when i execute it,
    problem starts when i try to automate using a job in sql agent, I created a new job. and when i schedule it…the job fails with following error.. i have deployed package on my machine,,
    do i need to deploy it on source sql server,,,

    error is as follows….

    Code: 0xC0016016 Source: Description: Failed to decrypt protected XML node “DTS:Password” with error 0x8009000B “Key not valid for use in specified state.”. You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available. End Error Code: 0xC0202009 Source: Package Connection manager “servername.SSISpackage name.username” Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D. An OLE DB record is available. Source: “Microsoft SQL Native Client” Hresult: 0x80040E4D Description: “Communication link failure”. An OLE DB record is available. Source: “Microsoft SQL Native Client” Hresult: 0x80040E4D… The package execution fa… The step failed.
    C:\Program Files\Microsoft SQL Server\90\DTS\Packages\PackageName

  13. Harsh said

    Very usefull. The author is a life saver 🙂

  14. n said

    Thanks a lot

  15. Anitha said


  16. Prakash said

    Precise information. Thanks a lot.

  17. Thanda said

    Thanks a million, this was very useful to me. Will be proud to share the knowledge with my collegues who have been deploying the packages in some very wrong way.

  18. Nagesh Rao said

    Excellent job in explaining the details with screenshots. This has helped me immensely. You must have spent lot of time in compiling the details.

    Keep up the good work.

  19. JCNET said

    My SSIS Sever is not an SQL Server. I was able to deploy my packages this way to it before, but now get

    Could not load file or assembly ‘Microsoft.SqlServer.DTSRuntimeWrap, Version=, Culture=neutral, PublicKeyToken=89845dcd8080cc91’ or one of its dependencies. The system cannot find the file specified. (Microsoft.SqlServer.ManagedDTS)

    As far as I know nothing has changed. I even tried deploying the package that is currently in place again.

    I have this MSDN post.

    Thanks for any help or information!

  20. Sanjay Gopal said

    Very Good and useful article.New comers can easily get in to this SSIS Deployment world, if they go through very clearly

  21. bithru said

    sufficient explanation to learners

  22. rahul said

    hi if we deploy on other machine then at time when we run execute package from store procedur that time did we need to configure connection.

  23. Tarik Jebbour said

    You rock dude, thanks a lot for a great and extremly detailed article, you helped me a greaaaat deal, thanks again.


  24. dh said

    great summary. well done.

  25. kumar said

    it was really useful !!!!!

  26. Asmed said

    thanks for posting this tutorial, it’s really helpfull.

  27. Inder said

    Hi Everyone,

    I have started into ssis recently from ssrs,,,My senior give me a task to edit and modify the existing package and i have done it, that included adding new columns to one table then modifying the query in data flow task and now the last part he want me to see how the changes coming on cube and he want me to work on cube changes, I have no idea what is the next step i have to follow , I have no clue what he meant by that, I hope if anyone can help me out regarding this.

    Thanx In Advance

  28. Janet said

    You’re the bomb! I’ve not been able to schedule jobs without permission errors since I started SQL2005. Working liked greased lightening now. THANKS.

  29. […] Deploying SSIS Packages in SQL Server 2005 September 2008 31 comments 4 […]

  30. Juan said

    Very straight foward explanation. Thank you!

  31. sunny said

    Can I deploy a ssis package developed using BIDS 2008 to BIDS 2005 .Is that possible .Are there any alternatives ??

  32. Anonymous said

    Thanks a lot, really nice tutorial! 🙂

  33. Prabhu Sevam said

    Thank you for sharing this information. It is very usefull for SSIS beginers.

    Prabhu Selvam

  34. msharma said

    Great article. Excatly what I needed. I am adding a link in my blog

  35. A said

    Can i copy Solution folder direclty and will it work … or i need to follow above steps …

  36. SaranVenkt said

    Solution folder is not required here. Once you build the project you will get deploymnet folder and Just copy the deployment folder in to server
    which contains all dtsx packages. Just follow above steps.

  37. Shailesh said

    Excellent Stuff…!!! Many Thanks.. 🙂

  38. Anonymous said

    One of the detailed post I have ever seen. Great Job man!

  39. […] There is a deployment utility for SSIS projects in the Business Intelligence Development Studio (BIDS). Here is a great article which explains its usage (also apply for SQL Server 2008): Deploying SSIS Packages in SQL Server 2005 […]

  40. Anonymous said

    Great Article

Leave a Reply

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

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

Google photo

You are commenting using your Google 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 )

Connecting to %s

<span>%d</span> bloggers like this: