How should you best read features from a database based on the result of joining two tables and meeting an attribute-based condition?

How should you best read features from a database based on the result of joining two tables and meeting an attribute-based condition?

• A. FeatureJoiner
• B. InlineQuerier
• C. Native database format reader
• D. SQLCreator or SQLExecutor

Answer: (D)

Pushing the join and the attribute-based filter to the database so the database engine performs the work is the most efficient approach. By using a SQL statement that joins the two tables and applies the condition, you let the database do the heavy lifting and return only the matching rows to FME. In this workflow, the SQL is created and executed within FME by the SQLCreator or SQLExecutor, which keeps query construction and execution tightly integrated with your data flow and ensures you pull back exactly what you need. Relying on a FeatureJoiner would require bringing separate feature streams into FME and performing the join there, which increases data movement and processing inside FME rather than leveraging the database's join capabilities. InlineQuerier can run a SQL query, but using SQLCreator/SQLExecutor provides a more direct, robust pattern for building and executing the necessary join with the attribute-based filter. The native database format reader reads data in its native form but does not inherently apply a cross-table join and filter unless those are already defined in the data source; pushing the join into SQL remains the clearer, more maintainable approach.

Pushing the join and the attribute-based filter to the database so the database engine performs the work is the most efficient approach. By using a SQL statement that joins the two tables and applies the condition, you let the database do the heavy lifting and return only the matching rows to FME. In this workflow, the SQL is created and executed within FME by the SQLCreator or SQLExecutor, which keeps query construction and execution tightly integrated with your data flow and ensures you pull back exactly what you need.

Relying on a FeatureJoiner would require bringing separate feature streams into FME and performing the join there, which increases data movement and processing inside FME rather than leveraging the database's join capabilities. InlineQuerier can run a SQL query, but using SQLCreator/SQLExecutor provides a more direct, robust pattern for building and executing the necessary join with the attribute-based filter. The native database format reader reads data in its native form but does not inherently apply a cross-table join and filter unless those are already defined in the data source; pushing the join into SQL remains the clearer, more maintainable approach.