When you override the object, database, schema, or role, you must follow some guidelines.
If you specify an SQL override query to override the custom query used for importing the metadata from Snowflake tables, specify a fully qualified table name.
When you specify both an SQL override and overrides to the database, schema, warehouse, or role from the advanced source properties, consider the following guidelines for the override combinations:
Override the SQL and role
If you override the SQL and the role of a Snowflake object, verify that the override role has access to the table selected in the mapping.
To override the SQL and the role, you can perform one of the following tasks:
•Grant the overriding role with the same access permissions as the role used for the Snowflake object that you selected in the mapping.
•Specify an override to the table from the advanced properties. The specified override table is used in the design time and the SQL override takes precedence at runtime.
Override the SQL, database, schema, and role
If you select a Snowflake object in a mapping and you specify both an SQL override and also override the database, schema, and role from the advanced properties, and the table does not exist in the overriding database, the mapping fails with a table1 not found error.
Specify a valid table name that corresponds to the overriding database and schema name.
SQL override ports
The SQL override ports must be the same as the connected ports in the field mapping.