Skip to main content

Understanding catalogs, schemas, tables, and columns

Understand the data hierarchy used in Infinite Data so you can navigate, request access, and write queries more precisely.

When to use this​

  • Use it when data names seem confusing.
  • Use it before requesting a whole schema or specific tables.
  • Use it to talk to managers and data owners in the same language.

Before you start​

  • Open Data Catalog or QueryMesh Explorer.
  • Choose a data domain you know.
  • Have an example table to follow along with.

Step by step​

  1. Start with the catalog, which represents a data set available in Infinite Data.
  2. Inside the catalog, open the schema to see groupings of related tables.
  3. Open a table to see its columns.
  4. Use the columns to understand what information the table offers.
  5. When requesting access, state the level you need: a whole schema, specific tables, or column and row restrictions.

What happens next​

  • Access requests become clearer and quicker to evaluate.
  • Queries are less prone to errors of naming or of choosing the wrong data.
  • Managers can apply least privilege more precisely.

Common errors​

  • Confusing a catalog with a schema: confirm the hierarchy in the tree.
  • Requesting a whole schema when you only need one table: it raises risk and can delay approval.
  • Ignoring sensitive columns: some may require masking or additional justification.

Good practice​

  • Use the smallest unit that meets the need.
  • Standardize names in requests and evidence.
  • Review the columns before running broad queries.

Next steps​