I have a transformation job with two Table Updates. Is it deterministic what order they are executed in? One needs to run before the other, but I don't want to have to repeat all the other transformation logic in two separate jobs and remember to keep them in sync when changes are made. I played with explicit transactions but it didn't help .
Thanks
Hey SRenk,
We had a similar requirement porting our ETL over to Matillion, support at the time advised us there is no way to guarantee the order in a transformation. We ended up using an orchestration to order them, if you have common logic you might consider staging the data in one transformation then additional transformation to update from there.
Common logic may be better addressed by a shared job. I learned it hard way, to keep two Orchestration jobs in sync, without using a shared job.
Now, i have just 4 shared jobs, which takes care of loading 120+ tables. of course, there is not much transformation involved, but dealing with multiple file types, formats, file naming conventions, unzzipped/zipped with static/dynamic names within-- far too many variations.
Also, this may be different from your requirement, but i just wanted to reiterate the power of shared job, if you have common/similar processing logic.