Skip to content
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.

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

Guide on commands to run dbt in production #464

Closed
clrcrl opened this issue Nov 18, 2020 · 1 comment
Closed

Guide on commands to run dbt in production #464

clrcrl opened this issue Nov 18, 2020 · 1 comment
Labels
enhancement Use to add new features to the docs priority: high Technical inaccuracy, missing/incorrect information, or broken links. Negatively affects workflows size: medium This change will take up to a week to address

Comments

@clrcrl
Copy link
Contributor

clrcrl commented Nov 18, 2020

We have a bit of this info here, but I think it's time we pull it into the docs.

I imagine the content would be something along the lines of:

Job 1: Prod run

0. dbt deps
1. dbt seed
2. dbt run
3. dbt test
4. dbt source snapshot-freshness # though I do this after deps

Schedule this on a regular cadence

Job 2: Full refresh run
(as above but with --full-refresh)
Schedule this weekly at a non-busy time

Job 3: CI run
(all the instructions for doing state modified runs)

  • info on considerations if not using dbt-Cloud — schema naming / tearing down the schema

Other things seen in the wild:

  • testing sources before running models
  • using operations to perform a blue-green deploy as part of your prod run
  • breaking up the DAG into subdags
@clrcrl clrcrl changed the title Guide on steps to run dbt in production Guide on commands to run dbt in production Nov 18, 2020
@runleonarun runleonarun added enhancement Use to add new features to the docs priority: high Technical inaccuracy, missing/incorrect information, or broken links. Negatively affects workflows size: medium This change will take up to a week to address labels Dec 13, 2021
@runleonarun
Copy link
Collaborator

Closing because we have these listed here: https://next.docs.getdbt.com/reference/dbt-commands

nghi-ly pushed a commit that referenced this issue May 2, 2024
REPO SYNC - Public to Private
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Use to add new features to the docs priority: high Technical inaccuracy, missing/incorrect information, or broken links. Negatively affects workflows size: medium This change will take up to a week to address
Projects
None yet
Development

No branches or pull requests

2 participants