WAREHOUSE_EVENT_HISTORY and QUERY_HISTORY views: New columns in output (Preview)

When this behavior change bundle is enabled, the output of the WAREHOUSE_EVENTS_HISTORY view in the the ACCOUNT_USAGE schema and the QUERY_HISTORY view in the ORGANIZATION_USAGE schema include the following new columns:

WAREHOUSE_EVENT_HISTORY in the ACCOUNT_USAGE schema:

Column name

Data type

Description

GENERATION

TEXT

The type of warehouse generation.

  • 1 if the warehouse is a generation 1 warehouse

  • 2 if the warehouse is a generation 2 warehouse

QUERY_HISTORY in the ORG_USAGE schema:

Column name

Data type

Description

GENERATION

TEXT

The type of warehouse generation.

  • 1 if the warehouse is a generation 1 warehouse

  • 2 if the warehouse is a generation 2 warehouse

RESOURCE_CONSTRAINT

TEXT

One of:

  • MEMORY_1X

  • MEMORY_1X_x86

  • MEMORY_16X

  • MEMORY_16X_x86

  • MEMORY_64X

  • MEMORY_64X_x86

This value is only available for WAREHOUSE_CONSISTENT events. Otherwise, this value is NULL.

In addition to the new columns, the following behavior change is also introduced:

Before the change:

Using any of CREATE WAREHOUSE, ALTER WAREHOUSE, or CREATE OR ALTER WAREHOUSE to SET or UNSET a RESOURCE_CONSTRAINT property to STANDARD_GEN_1 or STANDARD_GEN_2 was allowed.

After the change:

The RESOURCE_CONSTRAINT parameter no longer identifies the generation of a warehouse. You must use the GENERATION parameter to specify the warehouse generation. Warehouses that used the RESOURCE_CONSTRAINT parameter to identify the warehouse generation now use the GENERATION parameter.

Using any of CREATE, ALTER, or CREATE OR ALTER WAREHOUSE to SET or UNSET the RESOURCE CONSTRAINT property to STANDARD_GEN_1 or STANDARD_GEN_2 will generate an SQL error similar to:

SET/UNSET Cannot set/unset resource constraint to 'STANDARD_GEN_[12]'. Use the GENERATION property to set/unset warehouse hardware generation.

Ref: 2225