- Schema:
CORTEX_ SEARCH_ SERVING_ USAGE_ HISTORY view¶
Important
This view is only available in the organization account. For more information, see Premium views in the organization account.
This Organization Usage view can be used to query the hourly serving usage history of Cortex Search across all the accounts in your organization. The information in this view includes the number of serving credits consumed per hour for a Cortex Search Service. This view only contains credits consumed for serving, not the other costs associated with a Cortex Search Service. For more information, see Cost considerations.
- See also:
CORTEX_SEARCH_SERVING_USAGE_HISTORY view (Account Usage)
Columns¶
Organization-level columns
| Column Name | Data Type | Description |
|---|---|---|
| ORGANIZATION_NAME | VARCHAR | Name of the organization. |
| ACCOUNT_LOCATOR | VARCHAR | System-generated identifier for the account. |
| ACCOUNT_NAME | VARCHAR | User-defined identifier for the account. |
Additional columns
| Column Name | Data Type | Description |
|---|---|---|
| START_TIME | TIMESTAMP_LTZ | Start of the specified time range in which the Cortex Search serving usage took place. |
| END_TIME | TIMESTAMP_LTZ | End of the specified time range in which the Cortex Search usage took place. |
| DATABASE_NAME | VARCHAR | Name of the database in which the Cortex Search Service resides. |
| SCHEMA_NAME | VARCHAR | Name of the schema in which the Cortex Search Service resides. |
| SERVICE_NAME | VARCHAR | Name of the Cortex Search Service. |
| SERVICE_ID | NUMBER | ID of the Cortex Search Service. |
| CREDITS | NUMBER | Number of credits billed for Cortex Search serving usage based on the size of indexed data during the START_TIME and END_TIME window. |
Usage notes¶
- Latency for the view may be up to 24 hours.
- Serving credits are incurred per GB-mo of indexed data, metered at the second-level. One may get an estimate of the indexed data size for a given service using the credit rate defined in the Snowflake Service Consumption Table.
- This view may show small discrepancies in incurred cost from hour-to-hour based on the second-level metering.