Forum Discussion
Deployment Pipelines with Embedded SKU
Each dataset stands on its own, so it will require data to be able to work in each of the stages.
Your problem is something multiple customers are facing, and it is usually solved in 2 ways:
- Have a separate DB for each stage, so that dev/ test are loaded only with small amount of data. You can configure rules in a pipeline to control the connections across stages, so Prod is unaffected.
- If you only have 1 data source to retrieve the data, you can use M parameters to control the amount of data that's being pulled in dev/test. Through param rules you can control the values across stages and make sure Prod stage is unaffected.
sapientcompany deployment pipelines works with embedded SKUs as well.
Pipelines are comprised of workspaces, that behave like any other workspace. You can choose to assign them to separate capacities, ot have them on the same one. when they share the capacity, it behaves as any other capacity with multiple workspaces.
Thank you. So it is shared but do you know if a copy of the data is made for a dataset or if it is just metadata that gets copied? My concern is since it is shared then I will consume resources by having 3 copies of a large dataset.
Each dataset stands on its own, so it will require data to be able to work in each of the stages.
Your problem is something multiple customers are facing, and it is usually solved in 2 ways:
- Have a separate DB for each stage, so that dev/ test are loaded only with small amount of data. You can configure rules in a pipeline to control the connections across stages, so Prod is unaffected.
- If you only have 1 data source to retrieve the data, you can use M parameters to control the amount of data that's being pulled in dev/test. Through param rules you can control the values across stages and make sure Prod stage is unaffected.