• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 433
  • Last Modified:

Deploying SSIS package with configuration file

I deployed an SSIS package from my development machine to the server where it will run via management Studio. Then I manually copied the configuration file to the target server. When executing the package via Management Studio I specified the path to the config file on the target server (the one I copied manually) but when the package ran, it was looking for the configuration file path from my development machine. I do not even think it used the config file I copied, but rather data sources i specified before runnign the package.

My question is how do I deploy the configuration file along with SSIS package and prevent the package from trying to reference the old config file from the development machine?
  • 2
2 Solutions
ValentinoVBI ConsultantCommented:
"When executing the package via Management Studio "

That's probably the issue.  In SSMS, when you right-click a package and execute it through Run Package it will actually run on your local machine.  To avoid this it's better to create a SQL Agent Job (using the SQL Server Integration Services Package job step type).
ValentinoVBI ConsultantCommented:
In addition to the above: let's say your config file is configured to be located at D:\SSIS_config.  When running the package through SSMS it will use the file from your local D: partition.  Using a job it will use the D: partition on the SSIS server.
YZlatAuthor Commented:
Thank you!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

A proven path to a career in data science

At Springboard, we know how to get you a job in data science. With Springboard’s Data Science Career Track, you’ll master data science  with a curriculum built by industry experts. You’ll work on real projects, and get 1-on-1 mentorship from a data scientist.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now