Seeing who queried a table

Use Lineage to understand which people or accounts queried a table, and when it happened.

When to use this

• Use it in data usage investigations.
• Use it when the data owner wants to understand a table's consumption.
• Use it to support audits and access reviews.

Before you start

• Have the catalog, schema, and table names.
• Define the investigation's period.
• Have a role that lets you view the audit trail or lineage.

Step by step

1. Open the Lineage area, or use the Who queried? action on the table where available.
2. Enter or confirm the table you are investigating.
3. Choose the period.
4. Review the people, service accounts, and related queries.
5. Open the relevant details to understand the context.
6. Export evidence if needed.

What happens next

• You will see who queried the table within the period you chose.
• The evidence can support a review of data rules.
• Future queries keep being recorded as the product is used.

Common errors

• Naming a table without its catalog or schema: names can repeat.
• Too short a period: relevant queries may fall outside it.
• Reading a query as a problem without analyzing the purpose and the role.

Good practice

• Use lineage together with data rules to understand the context.
• Protect evidence exports.
• Review access when a sensitive table shows unexpected consumption.

Next steps

• Exporting evidence
• Investigating access denied
• Glossary