- or -
AcceptsThe names of one or more columns in a PDT or an aggregate table
sortkeys parameter lets you specify one or more columns of a persistent derived table (PDT) or an aggregate table on which to apply a regular sort key.
See the Dialect support for
sortkeyssection below for the list of dialects that support
You can also create an interleaved sort key by using
indexes instead. You cannot use both at the same time, but at least one is required.
sortkeysparameter works only with tables that are persistent, such as PDTs and aggregate tables.
sortkeysis not supported for derived tables without a persistence strategy.
In addition, the
sortkeysparameter is not supported for derived tables that are defined using
Generally speaking, a sort key should be applied to date or time columns in the table, and possibly to columns that will be used frequently as filters. More information can be found in the Amazon Redshift documentation.
These examples assume that you are working with a Redshift database so that you can use the
customer_day_facts persistent native derived table that has a sortkey on
date and rebuilds when the datagroup
order_datagroup is triggered:
customer_day_facts derived table that is based on a SQL query and has a sortkey on
customer_day_facts derived table that is based on a SQL query with a sortkey on
Dialect support for
The ability to use
sortkeys depends on the database dialect your Looker connection is using. In Looker 22.8, the following dialects support
Traditional SQL dialects (such as MySQL and Postgres) should use
sortkeyswill not work with these databases.