deployment - How to upload Parent child SSIS package to server -
Hi all I am very new to SSIS I got some SSIS package developed by some other person, this flat after package mapping. Reads data from files and stores in the database.
Flow: 1) To first extract the package into the flat file and in the table in the store 2) Then it calls the child package using the package package. 3) Then baby packages do some calculations and update the database table.
The SSIS database is using environment variables to get information.
Everything is working fine, but now I want to deploy it to the package on my client's server.
Q: Do I need to copy and paste from the bin folder and paste it on the client machine? What I tried: I copy the file from the bin folder and keep it on my local computer. Then I prepare a job in MSSQL and run the work. The package runs completely but later I changed the location of my project and the problem started, the work stopped. Problem: An error says that the location of the hair package is not available (as I have changed the status of my project file)
Please suggest what to do.
I am going to create many assumptions here so please correct me if I am wrong.
I am conveying this problem that currently within Package Manager, your Project.dtsx is connected to the package location within the Project folder. In this situation, you want to change it to some other place, although the package in the connection manager is still pointing to the project location.
If I were you, I would do the following:
Create a string variable
- PackageFolderPath -
C: \ CurrentPackagePath \ DBPackage. Dtsx
Now what you want to do is go to the package within the connection manager and add an expression for the connection string with the following under the properties:
â? ??? @ [User: PackageFolderPath] If you evaluate the expression, then you should give it the location you set up in your variable.
Please note that if you want to work on the development system, set up the package at the project location.
Now once you have Those are the setups, copy the files to the new server and under the SQL Agent job, under
Set Value tab and Y slim here you want to add the following:
\ Package.Variables [User: PackageFolderPath] Properties [Value]
Under the Value you want
It is located anywhere now the new location of the package should be picked up when it is run.
A better way to do this is to use the deployment utility and use an XML configuration variable on the package. However this should work in such a way.
Comments
Post a Comment