In a transformation job, I can inspect the SQL being generated from the UI, If I were to use a SQL component as my entry point for a transformation job, I can see the code embedded in the subsequent components that depend on this first. So, does matillion lazily precomputes this starting query, so if I use it in different places throughout the same job it doesn't do the same calculation over and over? If this is the case, awesome.
If it is not the case, what is the best way to handle this, 2 transformation jobs? the first one writing into a table and the second one just using it where needed?
Thanks,