Concepts → Snowflake Result Set

Overview

In 2026.3.0, Incorta introduced Direct Query Integration, enabling you to query live data directly from source systems such as Snowflake and visualize results instantly without traditional data ingestion or modeling. After configuring your cluster, you can query Snowflake data directly via a Snowflake view or result set, and then create an insight on top of it.

A Snowflake result set queries data directly from the Snowflake account configured in the Cluster Management Console (CMC), without requiring an Incorta physical schema table or business view to reference it.

Create a Snowflake result set

The following steps show how to create a Snowflake result set after you configure your environment.

1. Log in to the Incorta platform as an Analyzer user.
2. On the navigation pane, select Content.
3. Select a dashboard that you have Edit access to or create a new one.
4. Add a new insight to the dashboard, and then open it for editing.
5. In the Data panel, select Add New Result Set > Using Snowflake.
6. In the Snowflake dialog, enter the SQL query, and then select Done.

Referenceable objects and variables in query

In a Snowflake result set, you can reference only tables available in the Snowflake account configured in the CMC. You cannot reference Incorta physical or business schema objects. However, you can reference presentation variables in the WHERE clause using the getVar(var_name, "default_value") function.

Supported SQL and recommended queries

• The Snowflake result set supports the standard ANSI SQL syntax.
• You must provide an alias for computed columns, such as SUM() and AVG(), in the SQL query. Failing to use an alias will work in the Snowflake editor. However, you will face query execution failure when creating insights on top of the Snowflake result set.
• When you run SQL queries against your Snowflake data:
  • Use aggregated queries (such as SUM and AVG).
  • Avoid flat queries (such as SELECT *).

Examples

The following is an example of the SQL queries recommended for Snowflake result set:

Copy
SELECT
    STATE,
    SUM(SALES) AS TOTAL_SALES,
    SUM(PROFIT) AS TOTAL_PROFIT,
    RANK() OVER (ORDER BY SUM(SALES) DESC) AS SALES_RANK,
    RANK() OVER (ORDER BY SUM(PROFIT) DESC) AS PROFIT_RANK
FROM SALES_FLAT
GROUP BY STATE
ORDER BY SALES_RANK;

The following is an example of referencing a presentation variable using the getVar() function.

Copy
SELECT
    TPCH_SF1.ORDERS.O_ORDERSTATUS as Order_Status,
    TPCH_SF1.ORDERS.O_ORDERPRIORITY as Priority,
    TPCH_SF1.ORDERS.O_ORDERDATE as Date,
    sum(TPCH_SF1.ORDERS.O_TOTALPRICE) as sales
FROM TPCH_SF1.ORDERS
WHERE Order_Status = getVar(pv_sts, "P")
GROUP BY 1,2,3

Insights over Snowflake result sets

After defining a Snowflake result, you can create an Incorta insight based on it. Most of the features of the Incorta insight are available, except for the following:

• Runtime dashboard filters, including drilling down
• Dashboard filters and prompts, except for presentation variables
  Note

  To apply dashboard filters, use presentation variables directly in the SQL query with the following syntax: getVar(var_name, "default_value").

  This syntax works across all variable data types. No explicit type casting is required as non-string values are cast automatically.

Caching direct queries

To balance real-time data needs with system performance and resource efficiency, Incorta supports caching the direct query results. In addition to the global CMC option, you can specify the Cache Validity Duration at the Snowflake result set level, which overrides the global setting, providing flexible control over caching behavior for different workloads.

When a user opens an insight created on top of a Snowflake result set, the system checks the cache validity.

• If there is a valid cache, the insight displays cached data.
• If the cache has expired or there is no cache for the underlying query, the system automatically retrieves fresh data from the source, ensuring optimal performance without compromising data freshness.

Limitations

• The result of the Snowflake direct query must not exceed 1 million records. The Snowflake result set will be saved; however, the insight on top of it will fail to render. To change this limit, contact Incorta Support.
• Drilling down and dashboard runtime filters on insights based on Snowflake result sets are not supported.
• Prompts are not supported. Use presentation variables instead.
• Data lineage is not functioning properly for insights built on top of Snowflake result sets. The lineage displays the insight only, without any upstream or downstream nodes.
• Calculations within the direct query are handled by Snowflake and follow standard SQL null handling. However, calculations (formula columns) added at the insight level are handled by Incorta and respect its null handling behavior based on the Null Handling CMC option.