> For the complete documentation index, see [llms.txt](https://docs.tibero.com/tiberostudio.en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tibero.com/tiberostudio.en/about/sql-editor/sql-plan.md). # SQL Plan The users can view the execution plan of the created SQL. If The users need to tune the query, The users can do so to create the optimal SQL statement. The execution plan information is read from top to bottom, from inside to outside, starting with the task with the most indentation. The execution plan is available in two views: Tree and Text. ### Plan Info

The users can check the SQL ID, CHILD NUMBER, HASH VALUE, PLAN HASH VALUE, and executed SQL information related to the plan. ### Tree View

It displays the plan information in the form of a tree in the left area, and when The users focus on a specific row, the detailed plan information of the focused row is displayed in the right area. The main columns are as follows.

Name	Description
Operation	Indicates the specific operation performed by the database.
Option	Provides additional details about the operation
Object	The database object on which the operation is performed
Cost	The relative cost to run the query
Cardinality	The number of rows the job is expected to return
Partition State	The partition to start scanning
Partition Stop	The partition to end the scan on
CPU Cost	CPU usage cost
IO Cost	Disk I/O cost
Access Predicate	Conditions that determine how data is accessed
Filter Predicate	Conditions that filter data after it is read

### Text View

Displays the contents of all plans in the editor as text. ### --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.tibero.com/tiberostudio.en/about/sql-editor/sql-plan.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.