> For the complete documentation index, see [llms.txt](https://upsolver.gitbook.io/content/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://upsolver.gitbook.io/content/reference-1/monitoring/system-catalog/information-schema/tables.md).

# Tables

The **tables** system table includes information about the tables in your organization. 

From a worksheet within Upsolver, run the following query: 

```sql
SELECT * 
FROM system.information_schema.tables;
-- If you have a lot of tables, you can use LIMIT to reduce the result set 
-- LIMIT 50; 
```

The **system.information\_schema.tables** table includes the following columns:

<table><thead><tr><th width="165.33333333333331">Column</th><th width="125">Type</th><th>Description</th></tr></thead><tbody><tr><td>catalog</td><td>string</td><td>The name of the catalog used to store the table.</td></tr><tr><td>comment</td><td>string</td><td>An optional comment to describe the table.</td></tr><tr><td>created_at</td><td>datetime</td><td>The date and time when the table was created.</td></tr><tr><td>created_by</td><td>string</td><td>The name of the user who created the table.</td></tr><tr><td>format</td><td>string</td><td>The format of the table, e.g. hive, iceberg.</td></tr><tr><td>id</td><td>string</td><td>The unique identifier for the table.</td></tr><tr><td>is_external</td><td>Boolean</td><td>When this column returns TRUE, this is an Iceberg table managed by Upsolver, but which is not a target of an Iceberg ingestion job.</td></tr><tr><td>modified_at</td><td>datetime</td><td>The date and time when the table was last modified.</td></tr><tr><td>modified_by</td><td>string</td><td>The name of the user who modified the table.</td></tr><tr><td>name</td><td>string</td><td>The name of the table.</td></tr><tr><td>properties</td><td>string</td><td>See the <a href="#properties">Properties</a> table below.</td></tr><tr><td>schema</td><td>string</td><td>The schema in which the table resides.</td></tr><tr><td>status</td><td>string</td><td>The status of the table, e.g. running.</td></tr></tbody></table>

### Properties

The **properties** column comprises information on the options specified when the table was created:

<table><thead><tr><th width="293.3333333333333">Column</th><th width="135">Type</th><th>Description</th></tr></thead><tbody><tr><td>COMMENT</td><td>string</td><td>An optional comment to describe the table</td></tr><tr><td>COMPACTION_PROCESSES</td><td>integer</td><td>The number of compaction processes the table can do in parallel when it periodically compacts the data.</td></tr><tr><td>COMPRESSION</td><td>string</td><td>The type of compression for the table data.</td></tr><tr><td>COMPUTE_CLUSTER</td><td>string</td><td>The name of the compute cluster that processes the table.</td></tr><tr><td>DISABLE_COMPACTION</td><td>Boolean</td><td>Returns <code>TRUE</code> or <code>FALSE</code>. If <code>TRUE</code>, compaction is disabled.</td></tr><tr><td>EXPOSE_IN_CATALOG</td><td>Boolean</td><td>Returns <code>TRUE</code> or <code>FALSE</code> to determine if the table is exposed in the AWS Glue Data Catalog so it can be queried from data lake query engines.</td></tr><tr><td>GLOBALLY_UNIQUE_KEYS</td><td>Boolean</td><td>Returns <code>TRUE</code> or <code>FALSE</code> to define whether primary keys should be unique across partitions.</td></tr><tr><td>STORAGE_CONNECTION</td><td>string</td><td>The default storage connection configured for the metastore connection where the table is created.</td></tr><tr><td>STORAGE_LOCATION</td><td>string</td><td>The default storage location configured for the metastore connection where the table is created.</td></tr><tr><td>TABLE_DATA_RETENTION</td><td>string</td><td>The number of days that the data will be retained prior to deletion.</td></tr></tbody></table>

{% hint style="info" %}
For more information, please refer to the [Tables](/content/reference-1/sql-commands/tables.md) SQL command reference.&#x20;
{% endhint %}


---

# 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://upsolver.gitbook.io/content/reference-1/monitoring/system-catalog/information-schema/tables.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.