• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 440
  • 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?
0
YZlat
Asked:
YZlat
  • 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).
0
 
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.
0
 
YZlatAuthor Commented:
Thank you!
0
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

Cloud Class® Course: CompTIA Healthcare IT Tech

This course will help prep you to earn the CompTIA Healthcare IT Technician certification showing that you have the knowledge and skills needed to succeed in installing, managing, and troubleshooting IT systems in medical and clinical settings.

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