June 5, 2021 at 3:52 pm
Dear all,
I have a weird problem. Our client has in the MS SQL Server Integration Services Catalog, a parent Package deployed. That package calls some child packages using the Execute Package Task and calls the child ssis from the filesystem. I changed the child package, but it seems the parent package executes the previous version. I also tried to see if any error happens when I change the name of the package (like not found) but nothing happens and it runs. I am running the parent package from a job. I really don’t understand what is happening. Although the child Package is called from the filesystem, it is also deployed on the SSIS Catalog. Do I have to redeploy the Parent package in the ssis catalog?
Thank you in advance for your help!
June 6, 2021 at 4:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
June 7, 2021 at 8:07 am
Although the child Package is called from the filesystem, it is also deployed on the SSIS Catalog.
That doesn't make any sense. If the package is deployed in the Catalog you need to call it in the Catalog. If you're calling a version of is deployed in a File System method, but deployed a new version to the Catalog of course the called version is going to be "older", you haven't updated the package you are actually using. It's like opening a file in one located, making changes to it, saving it else where and then expecting the original to change too; unless you saved over the original it'll be the same as it was.
Why not swap to completely use SSIS Catalog in all instances? Mix and matching the deployment methods is going to be confusing, as you have already discovered.
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply