[{"data":1,"prerenderedAt":716},["ShallowReactive",2],{"navigation_docs_en":3,"-en-installation-dbt-profile":241,"-en-installation-dbt-profile-surround":713},[4,17,42,206,232],{"title":5,"redirect":6,"path":7,"stem":8,"children":9,"page":16},"Introduction","\u002Fen\u002Fintroduction\u002Fintroduction","\u002Fen\u002Fintroduction","en\u002F1.introduction",[10,12],{"title":5,"path":6,"stem":11},"en\u002F1.introduction\u002F1.introduction",{"title":13,"path":14,"stem":15},"Prerequisites","\u002Fen\u002Fintroduction\u002Fprerequisites","en\u002F1.introduction\u002F2.prerequisites",false,{"title":18,"redirect":19,"path":20,"stem":21,"children":22,"page":16},"Installation","\u002Fen\u002Finstallation\u002Fsetup","\u002Fen\u002Finstallation","en\u002F2.installation",[23,26,30,34,38],{"title":24,"path":19,"stem":25},"Machine set-up","en\u002F2.installation\u002F1.setup",{"title":27,"path":28,"stem":29},"A Tale of Two Repos","\u002Fen\u002Finstallation\u002Ftale-repos","en\u002F2.installation\u002F2.tale-repos",{"title":31,"path":32,"stem":33},"Database connection","\u002Fen\u002Finstallation\u002Fdbt-profile","en\u002F2.installation\u002F3.dbt-profile",{"title":35,"path":36,"stem":37},"Smoke-testing","\u002Fen\u002Finstallation\u002Fsmoke-testing","en\u002F2.installation\u002F4.smoke-testing",{"title":39,"path":40,"stem":41},"What now ?","\u002Fen\u002Finstallation\u002Fwhat-now","en\u002F2.installation\u002F5.what-now",{"title":43,"path":44,"stem":45,"children":46,"page":16},"Users Guide","\u002Fen\u002Fusing","en\u002F3.using",[47,50,54,88,188,202],{"title":5,"path":48,"stem":49},"\u002Fen\u002Fusing\u002Fintroduction","en\u002F3.using\u002F1.introduction",{"title":51,"path":52,"stem":53},"Running the ETL","\u002Fen\u002Fusing\u002Frunning","en\u002F3.using\u002F2.running",{"title":55,"path":56,"stem":57,"children":58,"page":16},"Configuration","\u002Fen\u002Fusing\u002Fconfiguration","en\u002F3.using\u002F3.configuration",[59,72,76,80,84],{"title":60,"path":61,"stem":62,"children":63,"page":16},"Architecture","\u002Fen\u002Fusing\u002Fconfiguration\u002Farchitecture","en\u002F3.using\u002F3.configuration\u002F1.architecture",[64,68],{"title":65,"path":66,"stem":67},"Overview","\u002Fen\u002Fusing\u002Fconfiguration\u002Farchitecture\u002Foverview","en\u002F3.using\u002F3.configuration\u002F1.architecture\u002F1.overview",{"title":69,"path":70,"stem":71},"Marts and reporting layer","\u002Fen\u002Fusing\u002Fconfiguration\u002Farchitecture\u002Fmarts-reporting","en\u002F3.using\u002F3.configuration\u002F1.architecture\u002F2.marts-reporting",{"title":73,"path":74,"stem":75},"Linking the databases","\u002Fen\u002Fusing\u002Fconfiguration\u002Fdatabases","en\u002F3.using\u002F3.configuration\u002F2.databases",{"title":77,"path":78,"stem":79},"Adapters and seeds","\u002Fen\u002Fusing\u002Fconfiguration\u002Fadapts-seeds","en\u002F3.using\u002F3.configuration\u002F3.adapts-seeds",{"title":81,"path":82,"stem":83},"Enabling a resource","\u002Fen\u002Fusing\u002Fconfiguration\u002Fenabling","en\u002F3.using\u002F3.configuration\u002F4.enabling",{"title":85,"path":86,"stem":87},"Overriding","\u002Fen\u002Fusing\u002Fconfiguration\u002Foverriding","en\u002F3.using\u002F3.configuration\u002F5.overriding",{"title":89,"redirect":90,"path":91,"stem":92,"children":93,"page":16},"Dashboards","\u002Fen\u002Fusing\u002F","\u002Fen\u002Fusing\u002Fdashboards","en\u002F3.using\u002F4.dashboards",[94,97,126,167,176,184],{"title":5,"path":95,"stem":96},"\u002Fen\u002Fusing\u002Fdashboards\u002Fintroduction","en\u002F3.using\u002F4.dashboards\u002F1.introduction",{"title":98,"redirect":99,"path":99,"stem":100,"children":101,"page":16},"Human resources","\u002Fen\u002Fusing\u002Fdashboards\u002Fhr","en\u002F3.using\u002F4.dashboards\u002F2. hr",[102,106,110,114,118,122],{"title":103,"path":104,"stem":105},"Employees leaves","\u002Fen\u002Fusing\u002Fdashboards\u002Fhr\u002Femp_conge","en\u002F3.using\u002F4.dashboards\u002F2. hr\u002F1.emp_conge",{"title":107,"path":108,"stem":109},"Active employees","\u002Fen\u002Fusing\u002Fdashboards\u002Fhr\u002Fempl_actif","en\u002F3.using\u002F4.dashboards\u002F2. hr\u002F2.empl_actif",{"title":111,"path":112,"stem":113},"Retirement","\u002Fen\u002Fusing\u002Fdashboards\u002Fhr\u002Fretirement","en\u002F3.using\u002F4.dashboards\u002F2. hr\u002F3.retirement",{"title":115,"path":116,"stem":117},"Efficacité","\u002Fen\u002Fusing\u002Fdashboards\u002Fhr\u002Fefficacite","en\u002F3.using\u002F4.dashboards\u002F2. hr\u002F4.efficacite",{"title":119,"path":120,"stem":121},"Absences des employé(e)s","\u002Fen\u002Fusing\u002Fdashboards\u002Fhr\u002Femp_abs","en\u002F3.using\u002F4.dashboards\u002F2. hr\u002F5.emp_abs",{"title":123,"path":124,"stem":125},"Resignation","\u002Fen\u002Fusing\u002Fdashboards\u002Fhr\u002Fresignation","en\u002F3.using\u002F4.dashboards\u002F2. hr\u002F6.resignation",{"title":127,"redirect":128,"path":128,"stem":129,"children":130,"page":16},"Educational service","\u002Fen\u002Fusing\u002Fdashboards\u002Feduc-serv","en\u002F3.using\u002F4.dashboards\u002F3.educ-serv",[131,135,139,143,147,151,155,159,163],{"title":132,"path":133,"stem":134},"Res epreuves","\u002Fen\u002Fusing\u002Fdashboards\u002Feduc-serv\u002Fres_epreuves","en\u002F3.using\u002F4.dashboards\u002F3.educ-serv\u002F1.res_epreuves",{"title":136,"path":137,"stem":138},"Students results monitoring","\u002Fen\u002Fusing\u002Fdashboards\u002Feduc-serv\u002Fsuivi_resultats","en\u002F3.using\u002F4.dashboards\u002F3.educ-serv\u002F2.suivi_resultats",{"title":140,"path":141,"stem":142},"Students headcount","\u002Fen\u002Fusing\u002Fdashboards\u002Feduc-serv\u002Feffectif_css","en\u002F3.using\u002F4.dashboards\u002F3.educ-serv\u002F3.effectif_css",{"title":144,"path":145,"stem":146},"Students absenteeism","\u002Fen\u002Fusing\u002Fdashboards\u002Feduc-serv\u002Fchronic_absenteeism","en\u002F3.using\u002F4.dashboards\u002F3.educ-serv\u002F4.chronic_absenteeism",{"title":148,"path":149,"stem":150},"Academic results","\u002Fen\u002Fusing\u002Fdashboards\u002Feduc-serv\u002Fres_scolaires","en\u002F3.using\u002F4.dashboards\u002F3.educ-serv\u002F5.res_scolaires",{"title":152,"path":153,"stem":154},"Predictive modelling - aggregated","\u002Fen\u002Fusing\u002Fdashboards\u002Feduc-serv\u002Fpredictive-aggregated","en\u002F3.using\u002F4.dashboards\u002F3.educ-serv\u002F6.predictive-aggregated",{"title":156,"path":157,"stem":158},"PEVR","\u002Fen\u002Fusing\u002Fdashboards\u002Feduc-serv\u002Fpevr","en\u002F3.using\u002F4.dashboards\u002F3.educ-serv\u002F7.pevr",{"title":160,"path":161,"stem":162},"Absenteeism","\u002Fen\u002Fusing\u002Fdashboards\u002Feduc-serv\u002Fabsenteeism","en\u002F3.using\u002F4.dashboards\u002F3.educ-serv\u002F8.absenteeism",{"title":164,"path":165,"stem":166},"Diplôme","\u002Fen\u002Fusing\u002Fdashboards\u002Feduc-serv\u002Fdiplome","en\u002F3.using\u002F4.dashboards\u002F3.educ-serv\u002F9.diplome",{"title":168,"redirect":169,"path":169,"stem":170,"children":171,"page":16},"School organisation","\u002Fen\u002Fusing\u002Fdashboards\u002Fschool-org","en\u002F3.using\u002F4.dashboards\u002F4.school-org",[172],{"title":173,"path":174,"stem":175},"Anomalies","\u002Fen\u002Fusing\u002Fdashboards\u002Fschool-org\u002Fanomalies","en\u002F3.using\u002F4.dashboards\u002F4.school-org\u002F1.anomalies",{"title":177,"path":178,"stem":179,"children":180,"page":16},"DirectionGenerale","\u002Fen\u002Fusing\u002Fdashboards\u002Fdirection_generale","en\u002F3.using\u002F4.dashboards\u002F5.direction_generale",[181],{"title":156,"path":182,"stem":183},"\u002Fen\u002Fusing\u002Fdashboards\u002Fdirection_generale\u002Fpevr","en\u002F3.using\u002F4.dashboards\u002F5.direction_generale\u002F1.pevr",{"title":185,"path":186,"stem":187},"Row Level Security","\u002Fen\u002Fusing\u002Fdashboards\u002Frls","en\u002F3.using\u002F4.dashboards\u002F5.rls",{"title":189,"redirect":90,"path":190,"stem":191,"children":192,"page":16},"Data marts","\u002Fen\u002Fusing\u002Fmarts","en\u002F3.using\u002F6.marts",[193,196,199],{"title":5,"path":194,"stem":195},"\u002Fen\u002Fusing\u002Fmarts\u002Fmarts","en\u002F3.using\u002F6.marts\u002F1.marts",{"title":127,"path":197,"stem":198},"\u002Fen\u002Fusing\u002Fmarts\u002Feducational-service","en\u002F3.using\u002F6.marts\u002F2.educational-service",{"title":98,"path":200,"stem":201},"\u002Fen\u002Fusing\u002Fmarts\u002Fhuman-resources","en\u002F3.using\u002F6.marts\u002F3.human-resources",{"title":203,"path":204,"stem":205},"Production checklist","\u002Fen\u002Fusing\u002Fproduction","en\u002F3.using\u002F7.production",{"title":207,"redirect":208,"path":209,"stem":210,"children":211,"page":16},"Developers Guide","\u002Fen\u002Fcontributing\u002Fgetting-started","\u002Fen\u002Fcontributing","en\u002F4.contributing",[212,215,223],{"title":213,"path":208,"stem":214},"Getting Started","en\u002F4.contributing\u002F1.getting-started",{"title":216,"redirect":217,"path":218,"stem":219,"children":220,"page":16},"Conventions","\u002Fen\u002Fcontributing\u002Fconventions\u002Fgetting-started","\u002Fen\u002Fcontributing\u002Fconventions","en\u002F4.contributing\u002F2.conventions",[221],{"title":213,"path":217,"stem":222},"en\u002F4.contributing\u002F2.conventions\u002F1.getting-started",{"title":224,"path":225,"stem":226,"children":227,"page":16},"Docs Ref","\u002Fen\u002Fcontributing\u002Fdocs","en\u002F4.contributing\u002F99.docs",[228],{"title":229,"path":230,"stem":231},"Components","\u002Fen\u002Fcontributing\u002Fdocs\u002Fcomponents","en\u002F4.contributing\u002F99.docs\u002F1.components",{"title":233,"redirect":6,"path":234,"stem":235,"children":236,"page":16},"Migrations","\u002Fen\u002Fmigrations","en\u002F5.migrations",[237],{"title":238,"path":239,"stem":240},"V0.17 -> V0.18","\u002Fen\u002Fmigrations\u002Fv0.17_to_v0.18","en\u002F5.migrations\u002F1.v0.17_to_v0.18",{"id":242,"title":31,"body":243,"description":707,"extension":708,"links":709,"meta":710,"navigation":427,"path":32,"seo":711,"stem":33,"__hash__":712},"docs_en\u002Fen\u002F2.installation\u002F3.dbt-profile.md",{"type":244,"value":245,"toc":698},"minimark",[246,251,260,268,280,283,286,296,299,311,315,328,341,344,379,385,439,442,448,459,462,515,519,535,541,549,559,566,586,605,617,623,627,641,645,651,679,694],[247,248,250],"h1",{"id":249},"you-know-nothing-can-we-start-from-the-basics","\"You know nothing\" : can we start from the basics ?",[252,253,254,255,259],"p",{},"For now, we haven't connected the Store to the database. To connect the Store to the database and start materializing our views and tables, we need to tell dbt where to look for the database credentials and connection information. We do this by creating a ",[256,257,258],"code",{},"profiles.yml"," file.",[261,262,264,265,267],"h2",{"id":263},"what-the-heck-is-a-profilesyml-file","What the heck is a ",[256,266,258],{}," file?",[269,270,272,273,275,276,279],"alert",{"type":271},"info","tl;dr: dbt uses a ",[256,274,258],{}," file saved under ",[256,277,278],{},"~\u002F.dbt\u002Fprofiles.yml"," to store the database connection information.",[252,281,282],{},"The need for a dbt profile file arises from the fact that dbt needs to know where your data is stored, how to connect to it, and other configuration details. By having a centralized configuration file, you can manage these settings in one place and switch between different environments (for example, development and production) without modifying your dbt models.",[252,284,285],{},"There are some key elements you might find in a dbt profile file:",[287,288,289,293],"ol",{},[290,291,292],"li",{},"Database connection details: It includes information such as the type of database (for example, BigQuery, Snowflake, Redshift, or SQL Server), host, database name, schema, and authentication details.",[290,294,295],{},"Profiles: You can define multiple profiles within the file, allowing you to switch between different environments or data warehouses easily.",[252,297,298],{},"In summary, the dbt profile file is essential for configuring and connecting dbt to your data warehouse, streamlining the data transformation process.",[252,300,301,302,306,307,310],{},"This file is ",[303,304,305],"strong",{},"not"," located in the project itself, because it contains credentials we don't want exposed through Git. Instead, it's usually located in the ",[256,308,309],{},"~\u002F.dbt"," folder.",[261,312,314],{"id":313},"how-does-dbt-know-which-profile-to-use","How does dbt know which profile to use?",[269,316,317,318,321,322,325,326,259],{"type":271},"tl;dr: the ",[256,319,320],{},"profile"," key at the top of ",[256,323,324],{},"cssXX.dashboards_store\u002Fdbt_project.yml"," refers to the profile you want to use from the ",[256,327,278],{},[252,329,330,331,333,334,336,337,340],{},"When you run dbt commands in a specific project, dbt determines which profile to use based on the configuration specified in the ",[256,332,258],{}," file. The ",[256,335,258],{}," file is typically located in the ",[256,338,339],{},"~\u002F.dbt\u002F"," directory.",[252,342,343],{},"Here's how dbt knows which profile to use for a specific project:",[287,345,346,360],{},[290,347,348,351],{},[303,349,350],{},"Default Profile:",[352,353,354],"ul",{},[290,355,356,357,359],{},"If you have a single profile in your ",[256,358,258],{}," file, dbt will use that profile by default. This is the case when you only have one environment or data warehouse connection.",[290,361,362,365],{},[303,363,364],{},"Project Configuration:",[352,366,367],{},[290,368,369,370,373,374,376,377,259],{},"In the ",[256,371,372],{},"dbt_project.yml"," file within your dbt project directory, you can specify the profile to use for that specific project using the ",[256,375,320],{}," key. If this key is not set, dbt will use the default profile from the ",[256,378,258],{},[252,380,381,382,384],{},"Example ",[256,383,372],{},":",[386,387,392],"pre",{"className":388,"code":389,"language":390,"meta":391,"style":391},"language-yaml shiki shiki-themes material-theme-lighter material-theme material-theme-palenight","name: my_project\nversion: 1.0\n\nprofile: my_custom_profile\n","yaml","",[256,393,394,410,422,429],{"__ignoreMap":391},[395,396,399,403,406],"span",{"class":397,"line":398},"line",1,[395,400,402],{"class":401},"swJcz","name",[395,404,384],{"class":405},"sMK4o",[395,407,409],{"class":408},"sfazB"," my_project\n",[395,411,413,416,418],{"class":397,"line":412},2,[395,414,415],{"class":401},"version",[395,417,384],{"class":405},[395,419,421],{"class":420},"sbssI"," 1.0\n",[395,423,425],{"class":397,"line":424},3,[395,426,428],{"emptyLinePlaceholder":427},true,"\n",[395,430,432,434,436],{"class":397,"line":431},4,[395,433,320],{"class":401},[395,435,384],{"class":405},[395,437,438],{"class":408}," my_custom_profile\n",[252,440,441],{},"In this example, dbt would use the profile named \"my_custom_profile\" for the \"my_project\" project.",[252,443,444,445,447],{},"By providing the profile information in the ",[256,446,372],{}," file, you can instruct dbt on which profile to use for a specific project.",[261,449,451,452,454,455,458],{"id":450},"what-is-the-difference-between-a-profile-and-a-target","What is the difference between a ",[256,453,320],{}," and a ",[256,456,457],{},"target","?",[252,460,461],{},"In the context of dbt, a profile and a target serve different purposes:",[287,463,464,489],{},[290,465,466,467],{},"Profile:",[352,468,469,475,478,481,484],{},[290,470,471,472,474],{},"A dbt profile is a configuration file named ",[256,473,258],{}," that contains information about your data warehouse connection.",[290,476,477],{},"It includes details such as the type of database (e.g., BigQuery, Snowflake, Redshift), host, database name, schema, and authentication details.",[290,479,480],{},"You can define multiple profiles within the profiles.yml file, allowing you to configure connections for different environments (e.g., development, production).",[290,482,483],{},"Profiles are mainly concerned with specifying how dbt connects to a data warehouse.",[290,485,486],{},[303,487,488],{},"The Dashboards Store should only use one profile.",[290,490,491,492],{},"Target:",[352,493,494,497,500,503,509],{},[290,495,496],{},"A dbt target is a specific environment or deployment of your dbt project.",[290,498,499],{},"Targets are configurations for running dbt commands in a specific context, such as development or production.",[290,501,502],{},"Targets are often specified using the --target flag when running dbt commands, allowing you to switch between different environments easily.",[290,504,505,506,508],{},"Targets can reference specific profiles within the ",[256,507,258],{}," file, allowing you to use different data warehouse connections for different environments.",[290,510,511,512,514],{},"In summary, a profile is the overall configuration for connecting dbt to a data warehouse and is defined in the ",[256,513,258],{}," file. A target, on the other hand, is a specific configuration for running dbt in a particular context or environment, and it can reference a specific profile. Targets help you manage and switch between different deployment environments for your dbt project.",[247,516,518],{"id":517},"got-it-i-need-a-profile-can-you-help-me-get-started","Got it. I need a profile. Can you help me get started ?",[269,520,522,523,526,527,531,532,534],{"type":521},"success","Configuring a profile can be cumbersome. Fortunately, when you bootstrapped the ",[256,524,525],{},"cssXX.dashboards_store",", you ",[528,529,530],"em",{},"actually"," created a ",[256,533,258],{}," sample that's almost ready to use.",[252,536,537,538,540],{},"When you bootstrapped the ",[256,539,525],{},", you were prompted for some information:",[352,542,543,546],{},[290,544,545],{},"What's your database IP ?",[290,547,548],{},"What's your database port ?",[252,550,551,552,554,555,558],{},"That information was used to render a ",[256,553,258],{}," sample, which you can find under ",[256,556,557],{},"cssXX.dashboards_store\u002Fprofiles-sample.yml",".",[252,560,561,562,565],{},"You now need to populate and move your ",[256,563,564],{},"profiles-sample.yml",". You can do so by:",[287,567,568,578],{},[290,569,570,571,573,574,577],{},"Adding your user's database password to connect to the database: edit the ",[256,572,564],{}," file, and replace ",[256,575,576],{},"password: dontLookAtMeImSecret"," with your user's actual password.",[290,579,580,581,583,584,384],{},"Move ",[256,582,564],{}," to ",[256,585,278],{},[386,587,591],{"className":588,"code":589,"language":590,"meta":391,"style":391},"language-bash shiki shiki-themes material-theme-lighter material-theme material-theme-palenight","mv profiles-sample.yml ~\u002F.dbt\u002Fprofiles.yml\n","bash",[256,592,593],{"__ignoreMap":391},[395,594,595,599,602],{"class":397,"line":398},[395,596,598],{"class":597},"sBMFI","mv",[395,600,601],{"class":408}," profiles-sample.yml",[395,603,604],{"class":408}," ~\u002F.dbt\u002Fprofiles.yml\n",[269,606,608,609,611,612,614,615,558],{"type":607},"danger","If you have already used dbt and have an existing ",[256,610,278],{},", just copy the content of ",[256,613,564],{}," to your existing ",[256,616,278],{},[247,618,620,621,458],{"id":619},"why-do-i-have-three-targets-in-my-profilesyml","Why do I have three targets in my ",[256,622,258],{},[261,624,626],{"id":625},"developing","Developing",[252,628,629,630,633,634,636,637,640],{},"You can see a target as an ",[256,631,632],{},"environment",". Targets allow dbt to handle the different environments you might have. The ",[256,635,258],{}," default target is ",[256,638,639],{},"dev",". Dev is configured to use your own name as a schema, and is the target you will mainly use to develop your models. Since it uses your name as a base database schema, every table you materialize and every code modification you make will not alter other people's materializations of the same project. By using targets, you can all work on the same project and the same database without stepping on each other's toes.",[261,642,644],{"id":643},"staging-and-production","Staging and production",[252,646,647,648,650],{},"The ",[256,649,258],{}," contains two other targets:",[287,652,653,667],{},[290,654,655,658,659,662,663,666],{},[303,656,657],{},"staging",": the staging target is used to test your code before deploying it to production. The staging target is configured to use the ",[256,660,661],{},"dbo"," schema in the ",[256,664,665],{},"store_dev"," database. You can use the staging schema to run your code at night and preview it before actually running against the production database.",[290,668,669,672,673,662,675,678],{},[303,670,671],{},"prod",": the prod target is used to deploy your code to production. It is configured to use the ",[256,674,661],{},[256,676,677],{},"store"," database. You should not explicitly use it unless you know what you are doing.",[252,680,681,682,685,686,688,689,685,691,693],{},"Ideally, your unreleased ",[303,683,684],{},"Power BI"," dashboards should be connected to the ",[256,687,657],{}," environment, and your released ",[303,690,684],{},[256,692,671],{}," environment. By doing so, you can test modifications to dashboards and scripts without affecting your end users.",[695,696,697],"style",{},"html pre.shiki code .swJcz, html code.shiki .swJcz{--shiki-light:#E53935;--shiki-default:#F07178;--shiki-dark:#F07178}html pre.shiki code .sMK4o, html code.shiki .sMK4o{--shiki-light:#39ADB5;--shiki-default:#89DDFF;--shiki-dark:#89DDFF}html pre.shiki code .sfazB, html code.shiki .sfazB{--shiki-light:#91B859;--shiki-default:#C3E88D;--shiki-dark:#C3E88D}html pre.shiki code .sbssI, html code.shiki .sbssI{--shiki-light:#F76D47;--shiki-default:#F78C6C;--shiki-dark:#F78C6C}html .light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html.light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html pre.shiki code .sBMFI, html code.shiki .sBMFI{--shiki-light:#E2931D;--shiki-default:#FFCB6B;--shiki-dark:#FFCB6B}",{"title":391,"searchDepth":412,"depth":412,"links":699},[700,702,703,705,706],{"id":263,"depth":412,"text":701},"What the heck is a profiles.yml file?",{"id":313,"depth":412,"text":314},{"id":450,"depth":412,"text":704},"What is the difference between a profile and a target?",{"id":625,"depth":412,"text":626},{"id":643,"depth":412,"text":644},"For now, we haven't connected the Store to the database. To connect the Store to the database and start materializing our views and tables, we need to tell dbt where to look for the database credentials and connection information. We do this by creating a profiles.yml file.","md",null,{},{"title":31,"description":707},"inylpKwmeTwiHWsO-hPHuD-tpUzOPtMqkyNCXHIUTr0",[714,715],{"title":27,"path":28,"stem":29,"description":391,"children":-1},{"title":35,"path":36,"stem":37,"description":391,"children":-1},1781106579549]