In an FME workflow, under which circumstance is using an SQLExecutor more appropriate than using an SQLCreator?

In an FME workflow, under which circumstance is using an SQLExecutor more appropriate than using an SQLCreator?

• A. If the input data for the workspace contained a point or area of interest.
• B. If the input data for the workspace contained a list of address IDs and you wanted to run an SQL statement for each one.
• C. If the input data for the workspace contained a text file with an SQL statement in it.
• D. If the input data for the workspace was in GeoJSON format.

Answer: (B)

The key idea is per-feature SQL execution. SQLExecutor is designed to run an SQL statement for every input feature, making it ideal when you have a list of values (like address IDs) and you want to run a separate query for each one. SQLCreator, by contrast, builds an SQL string from feature attributes, typically creating one statement to be executed (often in bulk or by another step), rather than driving multiple executions per input row. So when you need to perform a query for each ID in your list, SQLExecutor is the appropriate tool.

The key idea is per-feature SQL execution. SQLExecutor is designed to run an SQL statement for every input feature, making it ideal when you have a list of values (like address IDs) and you want to run a separate query for each one. SQLCreator, by contrast, builds an SQL string from feature attributes, typically creating one statement to be executed (often in bulk or by another step), rather than driving multiple executions per input row. So when you need to perform a query for each ID in your list, SQLExecutor is the appropriate tool.