Say you have multiple developers working on a model, I’m assuming they are all needing to run their data to look at it to see how its working. How do most people handle this? I dont have a schema for each user so the best I can think of would be that if you are working on a new feature or general development, you would need to name the tables with your username?
When it moves up to say “preprod” for testing, then I would expect a pipeline/svc account to execute it and this becomes a non-issue, same with “prod.”
How do others handle this development work to test out their model is working and code is generating correctly?
Here is a sample structure I came up with, does this make sense or would you recommend something different?
ample Structure for Prod (POC likely slightly different):
Branch Name: Austins New Feature
- Deployment location: Workspace Schema (Shared by everyone)
- Automation – none
- Table Name Examples:
- {Username}_{ModelName}_stgClaims
- {Username}_{ModelName}_intSumAndCount
- {Username}_{ModelName}_fctDatamartName
Branch Name: Development
- Deployment location: PreProd Schema
- Automation – On Commit AND/OR Schedule Defined
- Table Name Examples:
- {PreProd}_{ModelName}_stgClaims
- {PreProd}_{ModelName}_intSumAndCount
- {PreProd}_{ModelName}_fctDatamartName
Branch Name: Master/Main
- Deployment location: Production Schema
- Automation – On Commit AND/OR Schedule Defined
- Table Name Examples:
- {ModelName}_stgClaims
- {ModelName}_intSumAndCount
- {ModelName}_fctDatamartName
How would I go about renaming the tables in this structure? I’ve read through custom aliases but haven’t quite figured out how to do it.