NEWS, 26 AUG 2026, read 13 Nov 2026
Databricks masks SQL query text by default in system tables and APIs
Databricks' August 2026 release notes, entry dated 26 Aug 2026, say query text is now masked by default. Databricks gives the reason as SQL statements that may contain sensitive information. It lists three places: statement_text in system.query.history, query_text in the Query History and List Queries APIs, and SQL definition keys in request_params of system.access.audit.
The first two return the value REDACTED, and the audit keys are omitted. Account admins and members of the databricks_pii_access account group can read the unmasked text; an account admin creates that group and adds members. Dedicated access mode compute must run Databricks Runtime 15.4 LTS or above and the workspace must be enabled for serverless compute, or queries against the masked fields fail with an error.
This changes what an audit trail shows. A governance lead who relies on query history to prove who looked at a regulated field should confirm who sits in databricks_pii_access and whether the audit evidence still answers the question with masked text. Agent and copilot queries are logged in the same tables, so the group's membership decides who can reread the questions an agent asked.
More governance news
- Immuta adds dynamic review flows for data access requests, including agent requests4 Nov 2026
- Privacera release 9.2.48.1 changes PolicySync audit fields and Snowflake masking role evaluation4 Nov 2026
- Immuta custom securables extend access policies to dashboards, files and APIs28 Oct 2026
- Immuta warns Snowflake CREATE OR REPLACE can drop masking and row policies26 Oct 2026
Sources
- docs.databricks.com/aws/en/release-notes/product/2026/august, read 13 Nov 2026
Last reviewed 13 Nov 2026.