Skip to content

Updating SL Snowflake QS #8149

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: current
Choose a base branch
from
Open

Updating SL Snowflake QS #8149

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f20b5db
Updating SL Snowflake QS
matthewshaver Nov 7, 2025
be3e4ff
Update website/docs/guides/sl-snowflake-qs.md
matthewshaver Nov 7, 2025
48cf8f7
Update website/docs/guides/sl-snowflake-qs.md
matthewshaver Nov 20, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
44 changes: 7 additions & 37 deletions website/docs/guides/sl-snowflake-qs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -449,37 +449,9 @@ packages:

Copy link
Collaborator

@runleonarun runleonarun Nov 7, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hey @matthewshaver above this line ^ I see this dbt_utils reference:

packages:
 - package: dbt-labs/dbt_utils
   version: 1.1.1

Is this the old way and should it be replaced?

</File>

7. In the `models` directory, create the file `metrics/metricflow_time_spine.sql` in your main directory.
8. Copy the following query into the file and click **Save**.
7. Create a MetricFlow time spine model following the [MetricFlow time spine guide](/guides/mf-time-spine?step=1). This replaces the old dbt_utils approach and avoids deprecation warnings.

<File name='models/metrics/metricflow_time_spine.sql'>

```sql
{{
config(
materialized = 'table',
)
}}
with days as (
{{
dbt_utils.date_spine(
'day',
"to_date('01/01/2000','mm/dd/yyyy')",
"to_date('01/01/2027','mm/dd/yyyy')"
)
}}
),
final as (
select cast(date_day as date) as date_day
from days
)
select * from final

```

</File>

9. Enter `dbt run` in the command prompt at the bottom of the screen. You should get a successful run message and also see in the run details that dbt has successfully built five models.
8. Enter `dbt run` in the command prompt at the bottom of the screen. You should get a successful run message and also see in the run details that dbt has successfully built your models.

## Create semantic models

Expand Down Expand Up @@ -642,10 +614,7 @@ semantic_models:

To ensure accurate time-based aggregations, you must configure a [time spine](/docs/build/metricflow-time-spine). The time spine allows you to have accurate metric calculations over different time granularities.

1. Add a time spine model to your project at whichever granularity needed for your metrics (like daily or hourly).
2. Configure each time spine in a YAML file to define how MetricFlow recognizes and uses its columns. Follow the instructions in [Configuring time spine in YAML](/docs/build/metricflow-time-spine#configuring-time-spine-in-yaml) documenation.

For a step-by-step guide, refer to [MetricFlow time spine guide](/guides/mf-time-spine?step=1).
Follow the [MetricFlow time spine guide](/guides/mf-time-spine?step=1) for complete step-by-step instructions on creating and configuring your time spine model. This guide provides the current best practices and avoids deprecated configurations.

## Define metrics and add a second semantic model

Expand All @@ -658,7 +627,7 @@ In this section, you will [define metrics](#define-metrics) and [add a second se
There are different types of metrics you can configure:

- [Conversion metrics](/docs/build/conversion) &mdash; Track when a base event and a subsequent conversion event occur for an entity within a set time period.
- [Cumulative metrics](/docs/build/metrics-overview#cumulative-metrics) &mdash; Aggregate a measure over a given window. If no window is specified, the window will accumulate the measure over all of the recorded time period. Note that you must create the time spine model before you add cumulative metrics.
- [Cumulative metrics](/docs/build/cumulative) &mdash; Aggregate a measure over a given window. If no window is specified, the window will accumulate the measure over all of the recorded time period. Note that you must create the time spine model before you add cumulative metrics.
- [Derived metrics](/docs/build/metrics-overview#derived-metrics) &mdash; Allows you to do calculations on top of metrics.
- [Simple metrics](/docs/build/metrics-overview#simple-metrics) &mdash; Directly reference a single measure without any additional measures involved.
- [Ratio metrics](/docs/build/metrics-overview#ratio-metrics) &mdash; Involve a numerator metric and a denominator metric. A constraint string can be applied to both the numerator and denominator or separately to the numerator or denominator.
Expand Down Expand Up @@ -755,7 +724,8 @@ metrics:
type_params:
measure:
name: order_total
grain_to_date: month
cumulative_type_params:
grain_to_date: month
# Derived metric
- name: "pct_of_orders_that_are_large"
label: "pct_of_orders_that_are_large"
Expand Down Expand Up @@ -999,7 +969,7 @@ This section will guide you on how to use the Sigma integration to query your me
```sql
select * from
{{ semantic_layer.query (
metrics = ['order_total', 'order_count', 'large_orders', 'customers_with_orders', 'avg_order_value', pct_of_orders_that_are_large'],
metrics = ['order_total', 'order_count', 'large_orders', 'customers_with_orders', 'avg_order_value', 'pct_of_orders_that_are_large'],
group_by =
[Dimension('metric_time').grain('day') ]
) }}
Expand Down
Loading