> 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/views.md). # Views The **views** system table includes information about the materialized views that have been created within your organization. From a worksheet within Upsolver, run the following query: ```sql SELECT * FROM system.information_schema.views; ``` The **system.information\_schema.views** table includes the following columns:

Column	Type	Description
catalog	string	The name of the catalog used to store the view.
comment	string	An optional comment to describe the view.
created_at	datetime	The date and time when the view was created.
created_by	string	The name of the user who created the view.
id	string	The unique identifier for the view.
modified_at	datetime	The date and time when the view was modified.
modified_by	string	The name of the user who modified the view.
name	string	The name of the materialized view.
properties	string	See the Properties table below.
schema	string	The name of the schema used to store the view.

### Properties The **properties** column comprises information about the options specified when the materialized view was created:

Column	Type	Description
COMMENT	string	An optional comment to describe the view.
COMPUTE_CLUSTER	string	The compute cluster that runs the view.
MAX_TIME_TRAVEL_DURATION	integer	The number of days the state information maintained by the materialized view should be retained.
STORAGE_CONNECTION	string	The storage connection of the first table in the `FROM` statement in the view.
STORAGE_LOCATION	string	The storage location of the first table in the `FROM` statement in the view.
WINDOW	string	The maximum number of days to save the materialized view data before it is deleted.

--- # 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/views.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.