From 199402bf276253eedd7e66aea3619ff94f39e404 Mon Sep 17 00:00:00 2001 From: Jacob Marble Date: Wed, 18 Mar 2026 22:10:32 +0000 Subject: [PATCH] docs: add query tag documentation to Snowflake and Databricks connectors Document the automatic query tagging behavior for both connectors, including usage for monitoring, cost attribution, and debugging. --- .../Connectors/materialization-connectors/Snowflake.md | 10 ++++++++++ .../materialization-connectors/databricks.md | 10 ++++++++++ 2 files changed, 20 insertions(+) diff --git a/site/docs/reference/Connectors/materialization-connectors/Snowflake.md b/site/docs/reference/Connectors/materialization-connectors/Snowflake.md index 1ec10f2dbb3..5cbd1f1f124 100644 --- a/site/docs/reference/Connectors/materialization-connectors/Snowflake.md +++ b/site/docs/reference/Connectors/materialization-connectors/Snowflake.md @@ -313,6 +313,16 @@ Available options in Estuary include: You do not need to explicitly set the [`TIMESTAMP_TYPE_MAPPING` configuration](https://docs.snowflake.com/en/sql-reference/parameters#timestamp-type-mapping) in Snowflake. However, if you do, the value in Snowflake **must** match the value in Estuary. +## Query Tags + +The Snowflake connector automatically sets a [query tag](https://docs.snowflake.com/en/sql-reference/parameters#query-tag) on every session. The tag has the format `materialization_name:`, where `` is the full name of your Estuary materialization task. + +This requires no configuration. You can use query tags to: + +* **Monitor queries**: Filter [QUERY_HISTORY](https://docs.snowflake.com/en/sql-reference/functions/query_history) by `QUERY_TAG` to see all queries originating from a specific materialization. +* **Attribute costs**: Break down warehouse costs per materialization task using the query tag in your Snowflake usage reports. +* **Debug issues**: Quickly identify which materialization task generated a particular query. + ## Reserved words Snowflake has a list of reserved words that must be quoted in order to be used as an identifier. Estuary automatically quotes fields that are in the reserved words list. You can find this list in Snowflake's documentation [here](https://docs.snowflake.com/en/sql-reference/reserved-keywords.html) and in the table below. diff --git a/site/docs/reference/Connectors/materialization-connectors/databricks.md b/site/docs/reference/Connectors/materialization-connectors/databricks.md index 40011934c6a..a9cf6786e1c 100644 --- a/site/docs/reference/Connectors/materialization-connectors/databricks.md +++ b/site/docs/reference/Connectors/materialization-connectors/databricks.md @@ -142,6 +142,16 @@ SET TBLPROPERTIES ( ); ``` +## Query Tags + +The Databricks connector automatically sets a [query tag](https://docs.databricks.com/en/sql/user/queries/query-tags.html) on every session. The tag has the format `materialization_name:`, where `` is the full name of your Estuary materialization task. + +This requires no configuration. You can use query tags to: + +* **Monitor queries**: Filter the Databricks [query history](https://docs.databricks.com/en/sql/user/queries/query-history.html) to see all queries originating from a specific materialization. +* **Attribute costs**: Break down warehouse costs per materialization task using query tags. +* **Debug issues**: Quickly identify which materialization task generated a particular query. + ## Reserved words Databricks has a list of reserved words that must be quoted in order to be used as an identifier. Estuary automatically quotes fields that are in the reserved words list. You can find this list in Databricks's documentation [here](https://docs.databricks.com/en/sql/language-manual/sql-ref-reserved-words.html) and in the table below.