> For the complete documentation index, see [llms.txt](https://docs.dwh.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dwh.dev/features/data-catalog/fancy-sql-highlight.md).

# Fancy SQL Highlight

The static analyzer provides comprehensive information about all objects and columns at any point in an SQL query, making SQL highlighting more convenient and functional.\
\
In detailed object information and the DDL on the Lineage screen, you can observe SQL highlighting in this manner:

<figure><img src="/files/xG9xJN3UL83lYRyPl7m8" alt=""><figcaption><p>Clickable source objects</p></figcaption></figure>

Each object has an icon corresponding to its type and is clickable. Clicking on it will take you to the selected object. We distinguish all types of Snowflake objects - TABLE, VIEW, STAGE, STREAM, FUNCTION, etc.

Additionally, we've created a reference guide for core functions. Hovering over such a function in SQL, you'll see a brief description:

<figure><img src="/files/yrjuVzV6qDFZ3qADTRKD" alt=""><figcaption><p>Short function's description</p></figcaption></figure>

Clicking will expand the details and provide a link to the original documentation.


---

# 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.dwh.dev/features/data-catalog/fancy-sql-highlight.md?ask=<question>&goal=<endgoal>
```

`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.