Quickstart for dbt Cloud and Teradata

dbt Cloud

Quickstart

Teradata

Beginner

Menu

Introduction

In this quickstart guide, you'll learn how to use dbt Cloud with Teradata Vantage. It will show you how to:

• Create a new Teradata Clearscape instance
• Load sample data into your Teradata Database
• Connect dbt Cloud to Teradata.
• Take a sample query and turn it into a model in your dbt project. A model in dbt is a select statement.
• Add tests to your models.
• Document your models.
• Schedule a job to run.

Videos for you

You can check out dbt Fundamentals for free if you're interested in course learning with videos.

Prerequisites​

• You have a dbt Cloud account.
• You have access to a Teradata Vantage instance. You can provision one for free at https://clearscape.teradata.com. See the ClearScape Analytics Experience guide for details.

Related content

• Learn more with dbt Learn courses
• How we provision Teradata Clearscape Vantage instance
• CI jobs
• Deploy jobs
• Job notifications
• Source freshness

Load data

The following steps will guide you through how to get the data stored as CSV files in a public S3 bucket and insert it into the tables.

SQL IDE

If you created your Teradata Vantage database instance at https://clearscape.teradata.com and you don't have an SQL IDE handy, use the JupyterLab bundled with your database to execute SQL:

1. Navigate to ClearScape Analytics Experience dashboard and click the Run Demos button. The demo will launch JupyterLab.

2. In JupyterLab, go to Launcher by clicking the blue + icon in the top left corner. Find the Notebooks section and click Teradata SQL.

3. In the notebook's first cell, connect to the database using connect magic. You will be prompted to enter your database password when you execute it:

   %connect local

4. Use additional cells to type and run SQL statements.

1. Use your preferred SQL IDE editor to create two databases: jaffle_shop and stripe:

   CREATE DATABASE jaffle_shop AS PERM = 1e9;
   CREATE DATABASE stripe AS PERM = 1e9;

2. In the databases jaffle_shop and stripe, create three foreign tables and reference the respective csv files located in object storage:

CREATE FOREIGN TABLE jaffle_shop.customers (
    id integer,
    first_name varchar (100),
    last_name varchar (100)
 )
 USING (
    LOCATION ('/s3/dbt-tutorial-public.s3.amazonaws.com/jaffle_shop_customers.csv')
 )
 NO PRIMARY INDEX;

 CREATE FOREIGN TABLE jaffle_shop.orders (
    id integer,
    user_id integer,
    order_date date,
    status varchar(100)
 )
 USING (
    LOCATION ('/s3/dbt-tutorial-public.s3.amazonaws.com/jaffle_shop_orders.csv')
 )
 NO PRIMARY INDEX;

 CREATE FOREIGN TABLE stripe.payment (
    id integer,
    orderid integer,
    paymentmethod varchar (100),
    status varchar (100),
    amount integer,
    created date
 )
 USING (
    LOCATION ('/s3/dbt-tutorial-public.s3.amazonaws.com/stripe_payments.csv')
 )
 NO PRIMARY INDEX;   

Connect dbt cloud to Teradata

1. Create a new project in dbt Cloud. From Account settings (using the gear menu in the top right corner), click New Project.
2. Enter a project name and click Continue.
3. In Configure your development environment, click Add new connection.
4. Select Teradata, fill in all the required details in the Settings section, and test the connection.

dbt Cloud - Choose Teradata Connection

dbt Cloud - Teradata Account Settings

5. Enter your Development Credentials for Teradata with:

   • Username — The username of Teradata database.
   • Password — The password of Teradata database.
   • Schema — The default database to use
   dbt Cloud - Teradata Development Credentials

6. Click Test Connection to verify that dbt Cloud can access your Teradata Vantage instance.

7. If the connection test succeeds, click Next. If it fails, check your Teradata settings and credentials.

Set up a dbt Cloud managed repository

When you develop in dbt Cloud, you can leverage Git to version control your code.

To connect to a repository, you can either set up a dbt Cloud-hosted managed repository or directly connect to a supported git provider. Managed repositories are a great way to trial dbt without needing to create a new repository. In the long run, it's better to connect to a supported git provider to use features like automation and continuous integration.

To set up a managed repository:

1. Under "Setup a repository", select Managed.
2. Type a name for your repo such as bbaggins-dbt-quickstart
3. Click Create. It will take a few seconds for your repository to be created and imported.
4. Once you see the "Successfully imported repository," click Continue.

Initialize your dbt project​ and start developing

Now that you have a repository configured, you can initialize your project and start development in dbt Cloud:

1. Click Start developing in the IDE. It might take a few minutes for your project to spin up for the first time as it establishes your git connection, clones your repo, and tests the connection to the warehouse.
2. Above the file tree to the left, click Initialize your project to build out your folder structure with example models.
3. Make your initial commit by clicking Commit and sync. Use the commit message initial commit to create the first commit to your managed repo. Once you’ve created the commit, you can open a branch to add new dbt code.
4. You can now directly query data from your warehouse and execute dbt run. You can try this out now:
   • Click Create new file, add this query to the new file, and click Save as to save the new file:

     select * from jaffle_shop.customers
   • In the command line bar at the bottom, enter dbt run and click Enter. You should see a dbt run succeeded message.

Build your first model

You have two options for working with files in the dbt Cloud IDE:

• Create a new branch (recommended) — Create a new branch to edit and commit your changes. Navigate to Version Control on the left sidebar and click Create branch.
• Edit in the protected primary branch — If you prefer to edit, format, lint files, or execute dbt commands directly in your primary git branch. The dbt Cloud IDE prevents commits to the protected branch, so you will receive a prompt to commit your changes to a new branch.

Name the new branch add-customers-model.

1. Click the ... next to the models directory, then select Create file.
2. Name the file customers.sql, then click Create.
3. Copy the following query into the file and click Save.

with customers as (

   select
       id as customer_id,
       first_name,
       last_name

   from jaffle_shop.customers

),

orders as (

   select
       id as order_id,
       user_id as customer_id,
       order_date,
       status

   from jaffle_shop.orders

),

customer_orders as (

   select
       customer_id,

       min(order_date) as first_order_date,
       max(order_date) as most_recent_order_date,
       count(order_id) as number_of_orders

   from orders

   group by 1

),

final as (

   select
       customers.customer_id,
       customers.first_name,
       customers.last_name,
       customer_orders.first_order_date,
       customer_orders.most_recent_order_date,
       coalesce(customer_orders.number_of_orders, 0) as number_of_orders

   from customers

   left join customer_orders using (customer_id)

)

select * from final

4. Enter dbt run in the command prompt at the bottom of the screen. You should get a successful run and see the three models.

You can connect your business intelligence (BI) tools to these views and tables so they only read cleaned-up data rather than raw data in your BI tool.

Change the way your model is materialized

One of the most powerful features of dbt is that you can change the way a model is materialized in your warehouse, simply by changing a configuration value. You can change things between tables and views by changing a keyword rather than writing the data definition language (DDL) to do this behind the scenes.

By default, everything gets created as a view. You can override that at the directory level so everything in that directory will materialize to a different materialization.

1. Edit your dbt_project.yml file.

   • Update your project name to:

     dbt_project.yml

     name: 'jaffle_shop'

   • Configure jaffle_shop so everything in it will be materialized as a table; and configure example so everything in it will be materialized as a view. Update your models config block to:

     dbt_project.yml

     models:
       jaffle_shop:
         +materialized: table
         example:
           +materialized: view

   • Click Save.

2. Enter the dbt run command. Your customers model should now be built as a table!

   info

   To do this, dbt had to first run a drop view statement (or API call on BigQuery), then a create table as statement.

3. Edit models/customers.sql to override the dbt_project.yml for the customers model only by adding the following snippet to the top, and click Save:

   models/customers.sql

   {{
     config(
       materialized='view'
     )
   }}
   
   with customers as (
   
       select
           id as customer_id
           ...
   
   )
   

4. Enter the dbt run command. Your model, customers, should now build as a view.

   • BigQuery users need to run dbt run --full-refresh instead of dbt run to full apply materialization changes.

5. Enter the dbt run --full-refresh command for this to take effect in your warehouse.

FAQs

What materializations are available in dbt?

dbt ships with five materializations: view, table, incremental, ephemeral and materialized_view. Check out the documentation on materializations for more information on each of these options.

You can also create your own custom materializations, if required however this is an advanced feature of dbt.

Which materialization should I use for my model?

Start out with views, and then change models to tables when required for performance reasons (i.e. downstream queries have slowed).

Check out the docs on materializations for advice on when to use each materialization.

What model configurations exist?

You can also configure:

• tags to support easy categorization and graph selection
• custom schemas to split your models across multiple schemas
• aliases if your view/table name should differ from the filename
• Snippets of SQL to run at the start or end of a model, known as hooks
• Warehouse-specific configurations for performance (e.g. sort and dist keys on Redshift, partitions on BigQuery)

Check out the docs on model configurations to learn more.

Delete the example models

You can now delete the files that dbt created when you initialized the project:

1. Delete the models/example/ directory.

2. Delete the example: key from your dbt_project.yml file, and any configurations that are listed under it.

   dbt_project.yml

   # before
   models:
     jaffle_shop:
       +materialized: table
       example:
         +materialized: view
   dbt_project.yml

   # after
   models:
     jaffle_shop:
       +materialized: table

3. Save your changes.

FAQs

How do I remove deleted models from my data warehouse?

If you delete a model from your dbt project, dbt does not automatically drop the relation from your schema. This means that you can end up with extra objects in schemas that dbt creates, which can be confusing to other users.

(This can also happen when you switch a model from being a view or table, to ephemeral)

When you remove models from your dbt project, you should manually drop the related relations from your schema.

I got an "unused model configurations" error message, what does this mean?

You might have forgotten to nest your configurations under your project name, or you might be trying to apply configurations to a directory that doesn't exist.

Check out this article to understand more.

Build models on top of other models

As a best practice in SQL, you should separate logic that cleans up your data from logic that transforms your data. You have already started doing this in the existing query by using common table expressions (CTEs).

Now you can experiment by separating the logic out into separate models and using the ref function to build models on top of other models:

The DAG we want for our dbt project

1. Create a new SQL file, models/stg_customers.sql, with the SQL from the customers CTE in your original query.

2. Create a second new SQL file, models/stg_orders.sql, with the SQL from the orders CTE in your original query.

   models/stg_customers.sql

   select
      id as customer_id,
      first_name,
      last_name
   
   from jaffle_shop.customers
   models/stg_orders.sql

   select
      id as order_id,
      user_id as customer_id,
      order_date,
      status
   
   from jaffle_shop.orders

3. Edit the SQL in your models/customers.sql file as follows:

   models/customers.sql

   with customers as (
   
      select * from {{ ref('stg_customers') }}
   
   ),
   
   orders as (
   
      select * from {{ ref('stg_orders') }}
   
   ),
   
   customer_orders as (
   
      select
          customer_id,
   
          min(order_date) as first_order_date,
          max(order_date) as most_recent_order_date,
          count(order_id) as number_of_orders
   
      from orders
   
      group by 1
   
   ),
   
   final as (
   
      select
          customers.customer_id,
          customers.first_name,
          customers.last_name,
          customer_orders.first_order_date,
          customer_orders.most_recent_order_date,
          coalesce(customer_orders.number_of_orders, 0) as number_of_orders
   
      from customers
   
      left join customer_orders using (customer_id)
   
   )
   
   select * from final
   

4. Execute dbt run.

   This time, when you performed a dbt run, it created separate views/tables for stg_customers, stg_orders, and customers. dbt inferred the order in which these models should run. Because customers depends on stg_customers and stg_orders, dbt builds customers last. You don’t need to define these dependencies explicitly.

FAQs

How do I run one model at a time?

To run one model, use the --select flag (or -s flag), followed by the name of the model:

$ dbt run --select customers

Check out the model selection syntax documentation for more operators and examples.

Do ref-able resource names need to be unique?

Within one project: yes! To build dependencies between resources (such as models, seeds, and snapshots), you need to use the ref function, and pass in the resource name as an argument. dbt uses that resource name to uniquely resolve the ref to a specific resource. As a result, these resource names need to be unique, even if they are in distinct folders.

A resource in one project can have the same name as a resource in another project (installed as a dependency). dbt uses the project name to uniquely identify each resource. We call this "namespacing." If you ref a resource with a duplicated name, it will resolve to the resource within the same namespace (package or project), or raise an error because of an ambiguous reference. Use two-argument ref to disambiguate references by specifying the namespace.

Those resource will still need to land in distinct locations in the data warehouse. Read the docs on custom aliases and custom schemas for details on how to achieve this.

As I create more models, how should I keep my project organized? What should I name my models?

There's no one best way to structure a project! Every organization is unique.

If you're just getting started, check out how we (dbt Labs) structure our dbt projects.

Build models on top of sources

Sources make it possible to name and describe the data loaded into your warehouse by your extract and load tools. By declaring these tables as sources in dbt, you can:

• Select from source tables in your models using the {{ source() }} function, helping define the lineage of your data
• Test your assumptions about your source data
• Calculate the freshness of your source data

1. Create a new YML file, models/sources.yml.

2. Declare the sources by copying the following into the file and clicking Save.

   models/sources.yml

   version: 2
   
   sources:
      - name: jaffle_shop
        description: This is a replica of the Postgres database used by the app
        database: raw
        schema: jaffle_shop
        tables:
            - name: customers
              description: One record per customer.
            - name: orders
              description: One record per order. Includes canceled and deleted orders.

3. Edit the models/stg_customers.sql file to select from the customers table in the jaffle_shop source.

   models/stg_customers.sql

   select
      id as customer_id,
      first_name,
      last_name
   
   from {{ source('jaffle_shop', 'customers') }}

4. Edit the models/stg_orders.sql file to select from the orders table in the jaffle_shop source.

   models/stg_orders.sql

   select
      id as order_id,
      user_id as customer_id,
      order_date,
      status
   
   from {{ source('jaffle_shop', 'orders') }}

5. Execute dbt run.

   Your dbt run results will be the same as those in the previous step. Your stg_customers and stg_orders models will still query from the same raw data source in Teradata. By using source, you can test and document your raw data and also understand the lineage of your sources.

Add tests to your models

Adding tests to a project helps validate that your models are working correctly.

To add tests to your project:

1. Create a new YAML file in the models directory, named models/schema.yml

2. Add the following contents to the file:

   models/schema.yml

   version: 2
   
   models:
     - name: customers
       columns:
         - name: customer_id
           tests:
             - unique
             - not_null
   
     - name: stg_customers
       columns:
         - name: customer_id
           tests:
             - unique
             - not_null
   
     - name: stg_orders
       columns:
         - name: order_id
           tests:
             - unique
             - not_null
         - name: status
           tests:
             - accepted_values:
                 values: ['placed', 'shipped', 'completed', 'return_pending', 'returned']
         - name: customer_id
           tests:
             - not_null
             - relationships:
                 to: ref('stg_customers')
                 field: customer_id
   

3. Run dbt test, and confirm that all your tests passed.

When you run dbt test, dbt iterates through your YAML files, and constructs a query for each test. Each query will return the number of records that fail the test. If this number is 0, then the test is successful.

FAQs

What tests are available for me to use in dbt? Can I add my own custom tests?

Out of the box, dbt ships with the following tests:

• unique
• not_null
• accepted_values
• relationships (i.e. referential integrity)

You can also write your own custom schema data tests.

Some additional custom schema tests have been open-sourced in the dbt-utils package, check out the docs on packages to learn how to make these tests available in your project.

Note that although you can't document data tests as of yet, we recommend checking out this dbt Core discussion where the dbt community shares ideas.

How do I test one model at a time?

Running tests on one model looks very similar to running a model: use the --select flag (or -s flag), followed by the name of the model:

dbt test --select customers

Check out the model selection syntax documentation for full syntax, and test selection examples in particular.

One of my tests failed, how can I debug it?

To debug a failing test, find the SQL that dbt ran by:

• dbt Cloud:

  • Within the test output, click on the failed test, and then select "Details"

• dbt Core:

  • Open the file path returned as part of the error message.
  • Navigate to the target/compiled/schema_tests directory for all compiled test queries

Copy the SQL into a query editor (in dbt Cloud, you can paste it into a new Statement), and run the query to find the records that failed.

Does my test file need to be named `schema.yml`?

No! You can name this file whatever you want (including whatever_you_want.yml), so long as:

• The file is in your models/ directory¹
• The file has .yml extension

Check out the docs for more information.

¹If you're declaring properties for seeds, snapshots, or macros, you can also place this file in the related directory — seeds/, snapshots/ and macros/ respectively.

Why do model and source yml files always start with `version: 2`?

Once upon a time, the structure of these .yml files was very different (s/o to anyone who was using dbt back then!). Adding version: 2 allowed us to make this structure more extensible.

Resource yml files do not currently require this config. We only support version: 2 if it's specified. Although we do not expect to update yml files to version: 3 soon, having this config will make it easier for us to introduce new structures in the future

What tests should I add to my project?

We recommend that every model has a test on a primary key, that is, a column that is unique and not_null.

We also recommend that you test any assumptions on your source data. For example, if you believe that your payments can only be one of three payment methods, you should test that assumption regularly — a new payment method may introduce logic errors in your SQL.

In advanced dbt projects, we recommend using sources and running these source data-integrity tests against the sources rather than models.

When should I run my tests?

You should run your tests whenever you are writing new code (to ensure you haven't broken any existing models by changing SQL), and whenever you run your transformations in production (to ensure that your assumptions about your source data are still valid).

Document your models

Adding documentation to your project allows you to describe your models in rich detail, and share that information with your team. Here, we're going to add some basic documentation to our project.

1. Update your models/schema.yml file to include some descriptions, such as those below.

   models/schema.yml

   version: 2
   
   models:
     - name: customers
       description: One record per customer
       columns:
         - name: customer_id
           description: Primary key
           tests:
             - unique
             - not_null
         - name: first_order_date
           description: NULL when a customer has not yet placed an order.
   
     - name: stg_customers
       description: This model cleans up customer data
       columns:
         - name: customer_id
           description: Primary key
           tests:
             - unique
             - not_null
   
     - name: stg_orders
       description: This model cleans up order data
       columns:
         - name: order_id
           description: Primary key
           tests:
             - unique
             - not_null
         - name: status
           tests:
             - accepted_values:
                 values: ['placed', 'shipped', 'completed', 'return_pending', 'returned']
         - name: customer_id
           tests:
             - not_null
             - relationships:
                 to: ref('stg_customers')
                 field: customer_id

2. Run dbt docs generate to generate the documentation for your project. dbt introspects your project and your warehouse to generate a JSON file with rich documentation about your project.

3. Click the book icon in the Develop interface to launch documentation in a new tab.

FAQs

How do I write long-form explanations in my descriptions?

If you need more than a sentence to explain a model, you can:

1. Split your description over multiple lines using >. Interior line breaks are removed and Markdown can be used. This method is recommended for simple, single-paragraph descriptions:

  version: 2

  models:
  - name: customers
    description: >
      Lorem ipsum **dolor** sit amet, consectetur adipisicing elit, sed do eiusmod
      tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam,
      quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo
      consequat.

2. Split your description over multiple lines using |. Interior line breaks are maintained and Markdown can be used. This method is recommended for more complex descriptions:

  version: 2

  models:
  - name: customers
    description: |
      ### Lorem ipsum

      * dolor sit amet, consectetur adipisicing elit, sed do eiusmod
      * tempor incididunt ut labore et dolore magna aliqua.

3. Use a docs block to write the description in a separate Markdown file. b

How do I access documentation in dbt Explorer?

If you're using dbt Cloud to deploy your project and have the Team or Enterprise plan, you can use dbt Explorer to view your project's resources (such as models, tests, and metrics) and their lineage to gain a better understanding of its latest production state.

Access dbt Explorer in dbt Cloud by clicking the Explore link in the navigation. You can have up to 5 read-only users access the documentation for your project.

dbt Cloud developer plan and dbt Core users can use dbt Docs, which generates basic documentation but it doesn't offer the same speed, metadata, or visibility as dbt Explorer.

Commit your changes

Now that you've built your customer model, you need to commit the changes you made to the project so that the repository has your latest code.

If you edited directly in the protected primary branch:

1. Click the Commit and sync git button. This action prepares your changes for commit.
2. A modal titled Commit to a new branch will appear.
3. In the modal window, name your new branch add-customers-model. This branches off from your primary branch with your new changes.
4. Add a commit message, such as "Add customers model, tests, docs" and and commit your changes.
5. Click Merge this branch to main to add these changes to the main branch on your repo.

If you created a new branch before editing:

1. Since you already branched out of the primary protected branch, go to Version Control on the left.
2. Click Commit and sync to add a message.
3. Add a commit message, such as "Add customers model, tests, docs."
4. Click Merge this branch to main to add these changes to the main branch on your repo.

Deploy dbt

Use dbt Cloud's Scheduler to deploy your production jobs confidently and build observability into your processes. You'll learn to create a deployment environment and run a job in the following steps.

Create a deployment environment

1. In the upper left, select Deploy, then click Environments.
2. Click Create Environment.
3. In the Name field, write the name of your deployment environment. For example, "Production."
4. In the dbt Version field, select the latest version from the dropdown.
5. Under Deployment connection, enter the name of the dataset you want to use as the target, such as "Analytics". This will allow dbt to build and work with that dataset. For some data warehouses, the target dataset may be referred to as a "schema".
6. Click Save.

Create and run a job

Jobs are a set of dbt commands that you want to run on a schedule. For example, dbt build.

As the jaffle_shop business gains more customers, and those customers create more orders, you will see more records added to your source data. Because you materialized the customers model as a table, you'll need to periodically rebuild your table to ensure that the data stays up-to-date. This update will happen when you run a job.

1. After creating your deployment environment, you should be directed to the page for a new environment. If not, select Deploy in the upper left, then click Jobs.
2. Click Create one and provide a name, for example, "Production run", and link to the Environment you just created.
3. Scroll down to the Execution Settings section.
4. Under Commands, add this command as part of your job if you don't see it:
   • dbt build
5. Select the Generate docs on run checkbox to automatically generate updated project docs each time your job runs.
6. For this exercise, do not set a schedule for your project to run — while your organization's project should run regularly, there's no need to run this example project on a schedule. Scheduling a job is sometimes referred to as deploying a project.
7. Select Save, then click Run now to run your job.
8. Click the run and watch its progress under "Run history."
9. Once the run is complete, click View Documentation to see the docs for your project.

Congratulations 🎉! You've just deployed your first dbt project!

FAQs

What happens if one of my runs fails?

If you're using dbt Cloud, we recommend setting up email and Slack notifications (Account Settings > Notifications) for any failed runs. Then, debug these runs the same way you would debug any runs in development.