SQL History¶
SQL History displays SQL query records in the current workspace and lets you open an individual query to analyze its SQL text, results, and execution plan.
The SQL History entry point is controlled by a product feature flag. If SQL History does not appear in the sidebar, the entry point is not currently enabled for that workspace; it does not necessarily mean that query records do not exist.
Query history list¶
The list supports multidimensional filtering, sorting, pagination, column-display controls, and CSV downloads. Start with a small number of conditions, then add filters gradually to narrow the results.
Common information |
Purpose |
|---|---|
SQL text, query ID |
Locate a specific query |
State, query type |
Distinguish running, successful, and failed queries of different types |
Start time, end time, duration |
Determine when the query ran and assess its performance |
Database, user |
Confirm the context in which the query ran and who initiated it |
Session ID, transaction ID |
Correlate queries in the same session or transaction |
Rows read, bytes scanned, result count, CU |
Understand the query’s data scale and resource consumption |
Available filters include query type, time range, SQL text, duration, database, user, query ID, session ID, transaction ID, CU, and non-user execution. Refer to the current product version for the fields actually provided in the UI.
Query details¶
Click a query record in the list to view its details. The details page combines an overview of the query, the complete SQL text, query results, and execution plan.
Section |
Available information |
|---|---|
Query information |
State, time, user, database, query identifiers, and related statistics |
SQL text |
Complete statement, which can be copied for further analysis or reproduction |
Query results |
Execution result preview; use the download function provided on the page when you need to retain the results |
Query plan |
Execution nodes, data flow, statistics, and node details |
Use the execution plan to investigate slow queries. First inspect nodes or data flows with unusually high duration or data volume, then use the SQL text and query conditions to determine whether optimization is needed.
Recommended workflow¶
Filter by time range and state to determine whether the target query succeeded or failed.
Use the query ID, user, or SQL text to locate a specific record.
Open the details and first review the error information or total duration.
For performance issues, inspect the execution plan. For result issues, inspect the SQL text and result preview.
If the issue belongs to a workflow execution, return to Jobs to view the overall node states.
Scope¶
SQL History only records and analyzes query execution. It does not provide end-to-end workflow status, API auditing, or platform system logs. Do not use it as a workflow job center or cross-user operation audit log.
The retention range of query results, the number of previewable rows, and the downloadable content may change with backend policies. If results must be retained as business evidence, download and store them promptly using the capability provided by the product.