# Multiple Table Updates, execution order?
**URL:** https://matillioncommunity.discourse.group/t/multiple-table-updates-execution-order/1245
**Category:** Matillion ETL
**Created:** [January 27, 2021, 5:49pm UTC](https://matillioncommunity.discourse.group/t/multiple-table-updates-execution-order/1245 "2021-01-27T17:49:23Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@SRenk](https://matillioncommunity.discourse.group/u/SRenk)
#### Post date: [January 27, 2021, 5:49pm UTC](https://matillioncommunity.discourse.group/t/multiple-table-updates-execution-order/1245/1 "2021-01-27T17:49:23Z")
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
---
### Author:  [@BM213428](https://matillioncommunity.discourse.group/u/BM213428)
#### Post date: [January 29, 2021, 3:57am UTC](https://matillioncommunity.discourse.group/t/multiple-table-updates-execution-order/1245/2 "2021-01-29T03:57:17Z")
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.
---
### Author:  [@Murali](https://matillioncommunity.discourse.group/u/Murali)
#### Post date: [January 29, 2021, 3:44pm UTC](https://matillioncommunity.discourse.group/t/multiple-table-updates-execution-order/1245/3 "2021-01-29T15:44:06Z")
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.