TheQueries page in theDatabase section of theAdmin menu lists information about the last 50 queries that Looker submitted to your database. For information about queries that are older than the most recent 50 queries, see theUsage section of Looker.

Note: If you have a permission that provides access to only select pages in the Admin panel, such asmanage_schedules,manage_themes, orsee_admin, but you don't have theAdmin role, the page or pages that are described here may not be visible to you in the Admin panel.

Basic query information

Column	Definition
Time	The start time of the query, displayed in yourapplication time zone.
Status	The status of the query, which can include: Cache: Looker returned the results from its cache instead of running a duplicate query against the database. Complete: The query was completed successfully. Error: The query wasn't completed successfully because an error occurred, the details of which can be found by clicking theDetails button. Cancelled: The query was cancelled by Looker or the user. Waiting for PDT: The query needs to wait for apersistent derived table to be built before it can be executed. Building PDT: Apersistent derived table is in the process of being built. Queued: The query is waiting to be executed because too many queries are already in progress (queries can be limited by Looker in yourconnection setup or your database). Running: The query is in the process of being run. Unknown: Looker wasn't able to determine what happened with this query.
Connection	The Lookerconnection under which this query was run.
User	The user who ran this query, if that can be determined. Some queries are not executed by a specific user, such as when Looker creates apersistent derived table or when an unknown user accesses apublic Look.
Source	The source of the query in Looker, such as the Explore page or SQL Runner. If possible, a link to the saved Look, or thequery ID along with the name of the model and Explore, is also displayed. Some queries don't have additional information, such as those that are run in SQL Runner. Queries that are issued from theOpen SQL Interface have aSource value ofSql_interface.
Runtime	The time it took to run the query. This includes the construction of the query, any time the query spent in the queue, transit to and from the database, and database execution of the query. If the query is running, the runtime will show how long the query has been running. For queries that were run previously, the runtime will also show an estimate of how much time the query will take to finish running. The estimate is based on the duration of the last run of the query and will say something like "of about 2s".
Details Button	SeeThe Details Button subsection on this page for additional details.

The Details button

Clicking theDetails button to the right of any query will bring up additional information about that query. TheQuery Details menu includes the following:

• AnInfo section that includes details about the query (see the following table).
• ASQL section that shows the raw SQL that was executed against the database.Context Comments will not appear in theQuery Details information. To prevent comments from affecting query caching, Looker adds the context comments to outgoing SQL commands right before the SQL is sent to the database.
• ASQL Interface query section that appears when a query has been issued through theOpen SQL Interface. This section displays the SQL query that was sent to Looker from the external BI tool and can aid in troubleshooting and reproducing issues.
• AnOpen in SQL Runner link that will open the query inSQL Runner.

TheInfo section includes the following information:

Section	Definition
History ID	Thehistory ID of the query, if available.
Status	The status of the query, as described in thebasic query information table.
Message	If the query contains a PDT, thePDT generation comment appears in this field. If the query does not contain a PDT, the field does not appear.
Connection	The Lookerconnection under which this query was run.
User	The user who ran this query, if that can be determined. Some queries are not executed by a specific user, such as when Looker creates apersistent derived table or when an unknown user accesses apublic Look.
Source	The source of the query in Looker, such as theExplore page or SQL Runner. If possible, additional information is displayed, such as a link to the saved Look, thequery ID, model name, Explore name, or the fields that were selected.
Start Time	The start time of the query, displayed in yourapplication time zone.
End Time	The finish time of the query, displayed in yourapplication time zone.
Runtime	The length of time it took to run the query.

Query killing

For dialects that support query killing, Looker can stop a running query in two ways:

• Looker automatically stops a query if the user closes the browser tab in which the query is running.
• Looker admins can stop a running query from theQueries admin page by clicking theStop button for the query. (Users with thesee_queries permission can view theQueries page, but only Looker admins can stop a running query.)

Note: Google BigQuery connections that are configured forOAuth authentication don't support query killing.

For Looker to kill queries, either by closing the browser tab in which a query is running or by stopping the query in theQueries page, your database dialect must support query killing. The following table shows which dialects support query killing in the latest release of Looker:

Dialect	Supported?
Actian Avalanche
Amazon Athena
Amazon Aurora MySQL
Amazon Redshift
Amazon Redshift 2.1+
Amazon Redshift Serverless 2.1+
Apache Druid
Apache Druid 0.13+
Apache Druid 0.18+
Apache Hive 2.3+
Apache Hive 3.1.2+
Apache Spark 3+
ClickHouse
Cloudera Impala 3.1+
Cloudera Impala 3.1+ with Native Driver
Cloudera Impala with Native Driver
DataVirtuality
Databricks
Denodo 7
Denodo 8 & 9
Dremio
Dremio 11+
Exasol
Google BigQuery Legacy SQL
Google BigQuery Standard SQL
Google Cloud AlloyDB for PostgreSQL
Google Cloud PostgreSQL
Google Cloud SQL
Google Spanner
Greenplum
HyperSQL
IBM Netezza
MariaDB
Microsoft Azure PostgreSQL
Microsoft Azure SQL Database
Microsoft Azure Synapse Analytics
Microsoft SQL Server 2008+
Microsoft SQL Server 2012+
Microsoft SQL Server 2016
Microsoft SQL Server 2017+
MongoBI
MySQL
MySQL 8.0.12+
Oracle
Oracle ADWC
PostgreSQL 9.5+
PostgreSQL pre-9.5
PrestoDB
PrestoSQL
SAP HANA
SAP HANA 2+
SingleStore
SingleStore 7+
Snowflake
Teradata
Trino
Vector
Vertica

Query timeouts and queueing

Looker kills queries that have been waiting in queue for too long. This operation is called atimeout. Several timeouts may apply to your query:

• Connection pool timeout and maximum concurrent queries: To prevent overloading of your database with concurrent queries, Looker holds excess concurrent queries in the Looker query queue, and will kill queries that remain in queue for too long. By default, 75 maximum concurrent queries are allowed per connection. Additional queries beyond the connection limit will be timed out after 0 seconds. To change these defaults, configure theMax connections,Max concurrent queries for this connection, andConnection pool timeout settings on a connection'sConnections Settings page.

• Per-user query limit and timeout: To prevent any single user from filling up the Looker query queue, each user has a maximum number of allowed concurrent queries and a corresponding queue timeout for queries that are queued because of concurrent query limit. The per-user limit applies to both users who log in to Looker using the regular authentication process, and to users who log in using API user credentials. There are two ways you can define the maximum number of per-user concurrent queries for connections on your Looker instance:

  • Theper-user-query-limit startup option. This is an instance-wide setting that sets the default for connections on your instance. Theper-user-query-limit startup option limits the number of concurrent queries per user, per connection, per node on the Looker instance. The default maximum of 15 concurrent queries per user applies to each valid connection and, if your Looker instance isclustered, to each node in the cluster. By default, each user can run a maximum of 15 concurrent queries per connection, per node, with a timeout of 600 seconds. For example, if you have a 5-node cluster with aper-user-query-limit of 15, each node will allow 15 concurrent queries per user for this connection, for a total of 75 queries across all nodes (15 * 5 = 75).

  You can change the per-user query limit for a connection by using theMax concurrent queries per user for this connection setting on the connection'sConnection Settings page. If your Looker instance is customer-hosted, you can change the default maximum number of per-user concurrent queries by configuring the--per-user-query-limit startup option, and you can configure the queue timeout by using the--per-user-query-timeoutstartup option.

  • TheMax concurrent queries per user for this connection option in theConnections Settings for a connection. TheMax concurrent queries per user for this connection setting has a default of 25, and is per user and per connection, but not per node. For example, if you have a 5-node cluster and you set this value to 15, each node will allow 3 concurrent queries per user for this connection (15 / 5 = 3), for a total of 15 queries across all nodes. For a connection, if a value is provided for theMax concurrent queries per user for this connection setting, theMax concurrent queries per user for this connection value will override theper-user-query-limit startup option for the connection.

• Scheduler query limit and timeout: To prevent overloading of the Looker scheduler process, a Looker instance can run a maximum of 10 concurrent scheduled queries, and the timeout for queries in the scheduler queue is 1,200 seconds. If your Looker instance is customer-hosted, you can change these defaults by configuring the--scheduler-query-limit and--scheduler-query-timeoutstartup options.

  Note: If your Looker instance isclustered, then each node of the cluster uses its own scheduler queue. Thus, adding nodes to your cluster increases your total amount of allowed concurrent scheduled queries without placing additional burden on the Looker scheduler process.

• Renderer query limit and timeout: To prevent overloading of the Looker renderer process, a Looker instance can render a maximum of 2 concurrent image-based downloads, such as PDF and PNG formats. If your Looker instance is customer-hosted, you can change this default by configuring the--concurrent-render-jobsstartup option.

  Note: If your Looker instance isclustered, then each node of the cluster uses its own renderer queue. Thus, adding nodes to your cluster increases your total amount of allowed concurrent renderer jobs without placing additional burden on the Looker renderer process.

Webhook timeout: Looker will attemptdata delivery to a webhook for a maximum of 30 minutes. If Looker cannot communicate with the webhook destination in 30 minutes, the query will time out. This timeout is not configurable.

• Proxy timeout: Customer-hosted instances often use proxies with a default timeout of 60 seconds. We recommend that this timeout be increased to 60 minutes. See theRunning Looker behind a proxy server or load balancer Looker Community post for more information.

• Database timeout: Most databases have rules for queueing and timeouts that are independent of Looker's queues and timeouts. For example, a query may have left the Looker queue, but it can still be queued on your database. Check the documentation for your database for more information on customizing database query timeouts.