CAN QUERY

In the Ultra Transcenders books

DBX-GENAI

Each book explains CAN QUERY in context, with comparison tables and the common traps.

Terms in this definition

• View

  Shows a system through one chosen group of related concerns. No view is generic; each one is tied to whichever architecture it depicts.

• CAN MANAGE

  Outranking CAN VIEW and CAN QUERY, this is the strongest level you can hold on a serving endpoint or Databricks App, and changing who can use an endpoint requires it. Unity Catalog's MANAGE privilege is a different thing.

Related terms

• CDF

  Change data feed. When switched on for a Delta table it records which rows changed from version to version, exposing extra columns that give the kind of change and the commit version. You can query it with table_changes(), stream from it, or feed it to AUTO CDC.

• DML trigger

  Code that SQL Server runs automatically, inside the same transaction, whenever someone tries an INSERT, UPDATE or DELETE on a table or view. It can query the inserted and deleted tables to see what changed.

• Elastic query

  Lets Azure SQL Database run read-only Transact-SQL spanning multiple databases; it remains in preview. Managed Instance can query across databases natively instead.

• Enterprise exposure graph

  Exposure Management's map of assets, identities, findings and how they connect, fed by Entra ID, Defender for Cloud, Defender for Endpoint, Defender for Identity and connectors. Attack paths are built from it, and advanced hunting can query it.

• Event log

  Two different things share the name. A Lakeflow pipeline writes one you can query for progress, lineage and data quality metrics; a compute resource has an Event log tab showing its lifecycle, for example resizing or losing spot nodes, kept for 60 days.

• Inbound permissions

  Access levels controlling use of a serving endpoint, separate from anything it reaches outbound. CAN VIEW shows it in lists, CAN QUERY permits calling it too, and CAN MANAGE extends to editing, deleting and permission changes.

• Lineage system tables

  The system.access.table_lineage and system.access.column_lineage system tables, which record lineage events for reads and writes that you can query, kept on a rolling one-year basis.

• Managed Iceberg table

  Stores data in Apache Iceberg format (USING iceberg) as a Unity Catalog managed table. Engines outside Databricks can query and update it via the Iceberg REST Catalog API, and Unity Catalog handles its upkeep.