Skip to content

Latest commit

 

History

41 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

dbt models for Acme Co

Acme Co is a fictional client interested in modernizing their analytics stack. They want to use dbt to transform data in their warehouse, but need a better understanding of it’s capabilities before they can move forward.

The client uses Snowflake as their warehouse and this dataset can be found in the SUBSCRIPTION.RAW schema.
It represents 6 years of order data for Acme Co and is spread across 4 tables.
Acme Co ERD

  • Account:
    Represents customers

  • Order:
    Represents orders placed by customers
    Has 3 types ‘Create Subscription’, ‘Cancel Subscription’, ‘Change Subscription’.
    Has an ‘effective on’ date that represents when the order takes effect.
    Has a ‘booked on’ date that represents when the deal was closed.

  • Product:
    Represents a product Acme Corp sells
    Products are either “One Time” (they not recurring and don’t impact annually recurring revenue)
    or “Recurring” (they do impact annually recurring revenue).
    Products have a “Rate” which is their unit price per time period.
    Products have a Unit Timing which defines the period for recurring products.

  • Order-Product:
    Represents the changes in quantity for a specific product on an order.
    Example: Develop License product with quantity change 4 means the customer added 4 develop licenses.
    Churn Orders do not have product changes (they imply a loss of all annually recurring revenue).
    Renewal orders without product changes represent flat renewals.

About

dbt cloud exercise using Acme Co

Topics

Resources

Stars

0 stars

Watchers

1 watching

Forks

Releases

Packages

Contributors