This page refers to the
sql_table_nameparameter that is part of a
sql_table_namecan also be used as part of a view, described here
sql_table_namecan also be used as part of an explore, described here
sql_table_name is a child of
join is a child of
joins is a child of
|a table name in your database|
Typically the view on which a
join is based defines the table that will be queried.
However, you can use
sql_table_name to set the table in your database that will be queried by a
join. This is unusual, but can be useful when multiple tables have the same schema, allowing the same view to be used to describe all of them.
sql_table_name enables you to specify which of those tables should be used by the view you are joining. In such situations, you may also want to consider if using
extends would be useful.
If you need to reference a table from a different schema, you can use
schema_name.table_name. If you need to reference a table from a different database you can use
database_name.schema_name.table_name. However, please note that joins across databases require that the databases be on the same machine and be in the same SQL dialect.
If you don’t explicitly specify the schema, Looker will use the default that you have set. The default is configured in the Admin section of Looker under Connections.
Make the customer join rely on the customer_1 table from the default schema:
Make the customer explore rely on the customer_1 table from the analytics schema:
Tables Referenced By
sql_table_name Must Be Accessible From The Current Connection
sql_table_name will be used with a
join that is, in turn, part of a model. The model will have a database connection defined in it. Any table you reference in
sql_table_name must be accessible within that database connection.
Things to Know
To Name A
join Differently Than The Underlying Table, Apply
sql_table_name At The
In other words, instead of this: