The Queries page in the Database section of the Admin menu lists information about the last 50 queries that Looker submitted to your database. If you’d like to see information about queries older than that, check the Usage section of Looker.
Basic query information
| Column | Definition |
|---|---|
| Time | The start time of the query, displayed in your application time zone. |
| Status | The status of the query, which can include:
|
| Connection | The Looker connection 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 a persistent derived table or when an unknown user accesses a public 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 the query ID along with the name of the model and Explore, is also displayed. Some queries will not have additional information, such as those run in SQL Runner. |
| 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 currently 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 | See The Details Button subsection on this page for additional details. |
The Details Button
Clicking the Details button to the right of any query will bring up additional information about that query. The Query Details pop-up includes the following:
- An Info section that includes details about the query (see the following table).
- A SQL section that shows the raw SQL that was executed against the database. Context Comments will not appear in the Query 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.
- An Open in SQL Runner link that will open the query in SQL Runner.
The Info section includes the following information:
| Section | Definition |
|---|---|
| History ID | The history ID of the query, if available. |
| Status | The status of the query, as described above. |
| Connection | The Looker connection 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 a persistent derived table or when an unknown user accesses a public Look. |
| Source | The source of the query in Looker, such as the Explore page or SQL Runner. If possible, additional information is displayed, such as a link to the saved Look, the query ID, model name, Explore name, fields selected, and so on. |
| Start Time | The start time of the query, displayed in your application time zone. |
| End Time | The finish time of the query, displayed in your application time zone. |
| Runtime | The length of time it took to run the query. |
Query Killing
Looker will automatically stop a query that is still running when you close the browser tab in which the query is running. Looker admins can also stop a running query from the Queries page. (Users with the see_queries permission can view the Queries page, but only Looker admins can stop a running query.) Any query that is still running shows a Stop button to the right of the query. Click Stop to stop the query.
For Looker to kill queries, your database dialect must support query killing. The following list shows which dialects support query killing in Looker 22.6: