> For the complete documentation index, see [llms.txt](https://docs.secoda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secoda.co/integrations/data-warehouses/clickhouse/clickhouse-metadata-extracted.md).

# ClickHouse Metadata Extracted

List of all the metadata that Secoda pulls from ClickHouse

#### Metadata pulled <a href="#metadata-pulled" id="metadata-pulled"></a>

Secoda pulls the following metadata from ClickHouse:

* Tables
  * Name
  * Description
  * Schema
  * Database
  * External Usage (Popularity)
  * External Updated At
  * Byte Size
  * Rows
* Views
  * Name
  * Description
  * Schema
  * Database
  * External Usage (Popularity)
  * External Updated At
* Columns
  * Name
  * Description
  * Type
  * Foreign Key
  * Primary Key
* Column Profile
  * Min
  * Max
  * Median
  * STD Deviation
  * Value Distribution
  * Statistic Value Count
  * Percent Filled
  * Unique
* Creation Query
* Query History
  * SQL
  * User
  * Frequency
* Lineage
  * ClickHouse Column <-> ClickHouse Column
  * ClickHouse View <-> ClickHouse View
  * ClickHouse Table <-> ClickHouse Table
  * ClickHouse Table <-> ClickHouse View
  * ClickHouse Table <-> Dashboards from other sources
  * ClickHouse Table <-> Tables from other sources
  * ClickHouse Table, Views <-> Jobs from other sources
* Preview of first 50 rows (Optional)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.secoda.co/integrations/data-warehouses/clickhouse/clickhouse-metadata-extracted.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.