Forum Discussion
Creating 2nd Datamart in Workspace Error
- Anonymous3 years ago
Hi dlin37 ,
What is your operation before the error? Now you solve this problem? Could you please provide more details ? How many datamarts you have created?
Please have a check.
Considerations and limitations
- Datamarts are only available in Premium Gen 2 workspaces.
- Datamarts are not currently supported in Power BI embedded.
- Datamarts are not available in workspaces that are bound to an Azure Data Lake Gen2 storage account.
- Datamart extract, transform and load (ETL) operations can currently only run for up to 24 hours
- Datamarts currently officially support data volumes of up to 100 GB.
- Currently datamarts don’t support the currency data type, and such data types will be converted to float.
- Data sources behind a VNET or using private links can't currently be used with datamarts; to work around this limitation you can use an on-premises data gateway.
- Datamarts use port 1948 for connectivity to the SQL endpoint. Port 1433 needs to be open for datamarts to work.
- Datamarts only support Microsoft Azure Active Directory (Azure AD) and do not support managed identities or service principals at this time.
- Datamarts are currently not supported in Microsoft Teams.
- Datamarts currently support the following SQL clients:
- SSMS
- Azure Data Studio
- Datamarts aren't currently available in the following Azure regions:
- Sweden Central and South
- West India
- UAE Central
- Japan West
Datamarts are supported in all other Azure regions.
More details: Administration of datamarts (preview) - Power BI | Microsoft Docs
Best Regards
Community Support Team _ Polly
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi dlin37 ,
Does that make sense? If so, kindly mark my answer as the solution to close the case please. Thanks in advance.
Best Regards
Community Support Team _ Polly
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Issue resolved itself. It looks like the last update addressed the issue.