Skip to main content

02. Setting Up DBT Profiles

️ Setting Up DBT Profiles​

DBT profiles.yml is where you define database connection settings for DBT to connect to your data warehouse.


1. What is profiles.yml?​

  • A configuration file that stores credentials and connection settings.
  • DBT uses it to run models and execute queries.
  • It is stored in:
    • Linux/Mac: ~/.dbt/profiles.yml
    • Windows: %USERPROFILE%\.dbt\profiles.yml

2. Structure of profiles.yml​

A profile has:

  • Profile name (usually the same as your project name)
  • Target (environment: dev, prod)
  • Adapter settings (specific to your warehouse)

3. Example: Snowflake Profile​

my_dbt_project:    # Profile name
target: dev
outputs:
dev:
type: snowflake
account: your_account_name
user: your_username
password: your_password
role: your_role
warehouse: your_warehouse
database: your_database
schema: your_schema
threads: 4

4. Profile for BigQuery​

my_dbt_project:
target: dev
outputs:
dev:
type: bigquery
method: service-account
project: your_project_id
dataset: your_dataset
keyfile: /path/to/keyfile.json
threads: 4

5. Verify the Profile​

Run:

dbt debug

This checks:

  • If profiles.yml exists
  • If connection is successful

6. Multiple Environments​

You can define multiple targets like dev, prod:

my_dbt_project:
target: dev
outputs:
dev: {...}
prod: {...}

Switch targets using:

dbt run --target prod

Best Practices​

Never commit profiles.yml to Git Use environment variables for passwords:

password: "{{ env_var('DBT_PASSWORD') }}"


---

This includes:
**Frontmatter with ID, title, sidebar label**
**Emojis for better UX**
**Examples for Snowflake & BigQuery**
**Commands for verification**
**Next topic link for navigation**

---