Metadata storing in azure sql database and Capacity usage #63
|
Hi @bennyaustin I am really overwhelmed by seeing this prebuilt data platform and it seems very easy to implement. when am going through it i got couple of questions which i feel to ask.
|
Replies: 3 comments
|
Few others have asked similar questions. Thank you @Pavan-kumar-Narani for raising it here
|
|
Thank you @bennyaustin for your response As I heard this fabric accelerator supports automated deployments in one of the BLOG, but I see bicep templates only for storage account, keyvault, purview, fabric capacity creation and SQL db permissions. I am searching for how you are automating the deployments of fabric data pipeline, notebook, lakehouse and warehouse creation. Are you using any scripts for this. If am missing anything can you please guide me here how are you achieving this step in fabric accelerator ? |
|
@Pavan-kumar-Narani Fabric items are deployed when you sync your workspace to the Git fork. Steps 3 onwards in setup instructions after the Bicep deployment. |

Few others have asked similar questions. Thank you @Pavan-kumar-Narani for raising it here
Is there any reason for using Azure SQL Database to store its metadata as we have fabric warehouse instead, as sql db is outside of fabric? Maintaining controlDB as ASQL ensures the ELT Framework remains independent of the data platform tech stack. While the fabric accelerator is new, this ELT framework also supports accelerators for Azure Synapse and Azure Databricks. Additionally, feature-wise, the SQL database for Fabric is a better fit for migrating the control DB compared to DW. In fact, this is a planned feature for when the SQL database for Fabric goes GA; currently, it is in preview.
Wha…