Skip to main content

The difference between seeing metadata and querying data

Understand why seeing a table in the catalog does not necessarily mean you can query its rows.

When to use this​

  • Use it when a table appears in the catalog but the query is denied.
  • Use it when explaining the difference between data discovery and data use.
  • Use it to guide more precise access requests.

Before you start​

  • Have the table's name at hand.
  • Check whether the table appears in the catalog or in the Explorer.
  • Understand which information you actually need to query.

Step by step​

  1. Use the Data Catalog to discover that the table exists and which columns it has.
  2. Use QueryMesh Explorer to query data when access is granted.
  3. If the query is denied, identify whether the missing access is to the table, a column, or rows.
  4. Ask the manager for a data rule covering exactly what you need.
  5. After approval, wait for propagation and try again.

What happens next​

  • You will be able to tell a discovery problem from a query problem.
  • Managers can grant access without exposing more data than necessary.
  • The access decision is recorded in the audit trail.

Common errors​

  • Assuming every visible table can be queried.
  • Requesting access without stating the intended use.
  • Overlooking that a column may appear masked by a data protection.

Good practice​

  • Use metadata visibility to plan, not to assume access.
  • Request access only to the data you need.
  • Document why you need to query rows, not just see the table.

Next steps​