From the official release notes and blog. Every item points at the concepts worth re-reading.
A customer-managed key set on the system catalog can now be used to decrypt the statement_text and error_message fields in the query history system table. The release notes mark this generally available as of 2 October 2026. Teams that encrypt query history with their own key should read the docs section on reading encrypted fields.
Query tags are now generally available. You attach custom key-value tags to SQL workloads to group, filter and attribute cost on Databricks SQL warehouses and Lakehouse//RT compute. The tags show up in system.query.history and on the Query History page.
The system.query.history system table is now generally available. It provides account-wide records for queries run on SQL warehouses or serverless compute, including execution status, duration metrics, and query source.
Nothing of that kind yet.