July 25-26, 2023 — 7.25 Release Notes¶

Organization Usage: New QUERY_ACCELERATION_HISTORY View¶

With this release, we are pleased to announce the QUERY_ACCELERATION_HISTORY view in the Organization Usage schema of the shared SNOWFLAKE database. This view returns the query acceleration usage for warehouses across the accounts in your organization.

For more information, see QUERY_ACCELERATION_HISTORY view.

Snowflake Alerts: Support for Future Grants and Object Tagging¶

With this release, Snowflake alerts now support future grants and object tagging.

• You can use the FUTURE keyword in the GRANT <privileges> … TO ROLE command to define an initial set of privileges that should be granted on new alerts created in a specified database or schema.

• You can use the CREATE ALERT and ALTER ALERT commands to assign tags to Snowflake alerts.

• In the CREATE ALERT command, you can use WITH TAG or TAG to assign a tag to a newly created alert.

• In the ALTER ALERT command, you can use SET TAG or UNSET TAG to assign or remove a tag from an existing alert.

Search Optimization: Support for Substring Search in Semi-Structured Data — Preview¶

With this release, we are pleased to announce the preview of Search Optimization support for substring and regular expression search in semi-structured data, including ARRAY, OBJECT, and VARIANT columns. Previously, only equality searches on such columns could be optimized.

Substring queries include predicates that use the following keywords:

• LIKE, ILIKE, LIKE ANY, LIKE ALL, ILIKE ANY

• STARTSWITH, ENDSWITH, CONTAINS

• RLIKE, REGEXP, REXEP_LIKE

• SPLIT_PART (in equality predicates)

To enable search optimization of substring searches on semi-structured columns, use an ALTER TABLE … ADD SEARCH OPTIMIZATION command like one of those below.

ALTER TABLE mytable ADD SEARCH OPTIMIZATION ON SUBSTRING(semi_structured_column);

ALTER TABLE mytable ADD SEARCH OPTIMIZATION ON SUBSTRING(semi_structured_column:field);

ALTER TABLE mytable ADD SEARCH OPTIMIZATION ON SUBSTRING(semi_structured_column:field.nested_field);

The second and third commands illustrate enabling search optimization for a field within a column. Field names must be separated from the column name with a colon. Nested fields may be specified by including additional field names separated by periods, as shown in the third example.

For more information on this search optimization improvement, including its capabilities and limitations, see Search Optimization - Substring Search in VARIANT Types.

Access History: Track Masking & Row Access Policy References — General Availability¶

With this release, we are pleased to announce the general availability of the policies_referenced column in the Account Usage ACCESS_HISTORY view. This column allows for the monitoring of queries on a table or view protected by a row access policy and a column protected by a masking policy and the enforced masking and row access policies. The column includes support for intermediate objects and columns that are policy protected. Audits on policy protected objects and columns are easier because auditors have a more unified view of how protected data is referenced without having to do complex joins on multiple Account Usage views. This column was introduced in preview in February 2023.

For details, see Access History and the ACCESS_HISTORY view.

Create Named Stages using Snowsight — General Availability¶

With this release, we are pleased to announce the general availability of creating and editing named stages using Snowsight without writing SQL.

To create or edit named stages, you can enter details into Snowsight including information about authentication or encryption for the stage.

For more information, see Staging files using Snowsight.