[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-05 (世界標準時間)。"],[],[],null,["# Admin settings - Queries\n\n| **Note:** Looker admins can enable the [**Enhanced Query Admin**](/looker/docs/admin-panel-general-labs#enhanced_query_admin) experimental Labs feature to enhance the **Queries** page. The Labs feature improves performance on the **Queries** page, and it lists 500 paginated queries, rather than 50.\n\nThe **Queries** page in the **Database** section of the **Admin** 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 the [**Usage**](/looker/docs/admin-panel-server-usage) section of Looker.\n| **Note:** If you have a permission that provides access to only select pages in the Admin panel, such as [`manage_schedules`](/looker/docs/admin-panel-users-roles#manage_schedules), [`manage_themes`](/looker/docs/admin-panel-users-roles#manage_themes), or [`see_admin`](/looker/docs/admin-panel-users-roles#see_admin), but you don't have the [Admin role](/looker/docs/admin-panel-users-roles#default_roles), the page or pages that are described here may not be visible to you in the Admin panel.\n\nIf you have enabled the [Enhanced Query Admin](/looker/docs/admin-panel-general-labs#enhanced_query_admin) Labs feature, the **Queries** page displays the following tabs:\n\n- **Recent**: Displays queries that were run in the last hour. From this tab, Looker admins can cancel running queries.\n- **Complete**: Displays the most recent 500 queries.\n\nIf you haven't enabled the **Enhanced Query Admin** Labs feature, the **Queries** page lists the last 50 queries on a single page.\n\nBasic query information\n-----------------------\n\nThe Details button\n------------------\n\nClicking the **Details** button to the right of any query will bring up additional information about that query. The **Query Details** menu includes the following:\n\n- An **Info** section that includes details about the query (see the following table).\n- A **SQL** section that shows the raw SQL that was executed against the database. [**Context Comments**](/looker/docs/admin-panel-server-usage#sql_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.\n- A **SQL Interface query** section that appears when a query has been issued through the [Open SQL Interface](/looker/docs/sql-interface#identifying-sql-interface-queries-in-the-looker-ui). This section displays the SQL query that was sent to Looker from the external BI tool and can aid in troubleshooting and reproducing issues.\n- An **Open in SQL Runner** link that will open the query in [SQL Runner](/looker/docs/sql-runner-basics).\n\nThe **Info** section includes the following information:\n\nQuery killing\n-------------\n\nWhen you close the browser tab in which a query is running, Looker will automatically stop the query. Looker admins can also stop a running query from the **Queries** page. (Users with the [`see_queries` permission](/looker/docs/admin-panel-users-roles#see_queries) 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.\n\nFor Looker to kill queries, your database dialect must support query killing. The following list shows which dialects support query killing in the latest release of Looker:\n\nQuery timeouts and queueing\n---------------------------\n\nLooker kills queries that have been waiting in queue for too long. This operation is called a *timeout*. Several timeouts may apply to your query:\n\n- **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 the [Max connections](/looker/docs/connecting-to-your-db#max_connections), [**Max concurrent queries for this connection**](/looker/docs/connecting-to-your-db#max-queries), and [**Connection pool timeout**](/looker/docs/connecting-to-your-db#connection_pool_timeout) settings on a connection's [**Connections Settings**](/looker/docs/connecting-to-your-db) page.\n\n- **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. By default, each user can run a maximum of 15 concurrent queries, and the timeout is 600 seconds for queries that are queued because of this limit. These settings apply to both users who log in to Looker using the regular authentication process, and to users who log in using API user credentials. To change these defaults, configure the [Max concurrent queries per user for this connection](/looker/docs/connecting-to-your-db#max-queries-per-user) settings on a connection's [**Connections Settings**](/looker/docs/connecting-to-your-db) page. If your Looker instance is customer-hosted, you can change these defaults by configuring the `--per-user-query-limit` and `--per-user-query-timeout` [startup options](/looker/docs/startup-options).\n\n | **Note:** The default maximum of 15 concurrent queries per user applies to each valid connection and, if your Looker instance is [clustered](/looker/docs/clustering-looker), to each node in the cluster. For example, if a user has access to 2 valid connections, they can run a maximum of 30 concurrent queries, 15 per connection. If the user is on a clustered instance with 2 nodes and has access to 1 valid connection, they can run 30 concurrent queries, 15 per node. If the user has 2 valid connections on a clustered instance with 2 nodes, they can run a maximum of 60 concurrent queries, 15 for each connection on each node.\n- **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-timeout` [startup options](/looker/docs/startup-options).\n\n | **Note:** If your Looker instance is [clustered](/looker/docs/clustering-looker), 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.\n- **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-jobs` [startup option](/looker/docs/startup-options).\n\n | **Note:** If your Looker instance is [clustered](/looker/docs/clustering-looker), 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.\n\n\u003cbr /\u003e\n\n- **Webhook timeout** : Looker will attempt [data delivery to a webhook](/looker/docs/sharing-and-publishing/scheduling-and-sharing/send-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.\n - **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 the [Running Looker behind a proxy server or load balancer](https://discuss.google.dev/t/running-looker-behind-a-proxy-server-or-load-balancer/117104) Looker Community post for more information.\n\n - **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."]]
