SQL Statement: select a.*, b."CREW_NUM", b."CREW_LEADER"
from gas.primary_gas_vlv_maint a, sde.cfg_agol_user_lookup b
where b."USERNAME" = '@Value(EDITOR)';
Since your SQL statement doesn't have any conditions for joining table a and b, the statement performs CROSS JOIN on (table a) and (table b where USERNAME = EDITOR). Is it your intended query?
Result, the number of resulting features will be (the number of all records in table a) x (the number of records in table b whose USERNAME matches an EDITOR), every time whenever a feature is input. Naturally it could take a long time if the number of incoming features was large.
@srayford The article Merging or Joining Spreadsheet or Database Data gives ideas on the appropriate transformer to use for a particular type of join. SQLExecutor But as @takashi mentions, the SQL statement used will determine the results and possibly performance of the query.
At first I was trying to use SQLExecutor transformer that consisted of a SQL statement joining the 2 tables following this article: https://knowledge.safe.com/articles/19634/using-the-sqlexecutor-to-do-a-join.html
That was incredibly slow, so slow that I never got to the end of the process because it was taking too long. The SAFE representative Dan recommended I look into the InlineQuerier transformer. I was able to use the tables as inputs and then a SQL statement joining the 2 tables as the output. It worked for me and was fast. So the InlineQuerier transformer was my solution.
SQL Statement used in the InlineQuerier: select B.*, A.CREW_NUM, A.CREW_LEADER from "SDE.CFG_AGOL_USER_LOOKUP" A, "PRIMARYGASVALVE" B where A.USERNAME = B.EDITOR
