I recently had a spike on my fabric capacity with no user tagged against the query activity. After discussing with support this was identified as due to the eviction and recalculation caused by changing the storage mode on the semantic model from small to large.
This possibility of this CU spike is currently not documented and the blank user in the capacity metrics app also creates confusion.
Two suggested improvements.
1. Include this in the docs as a consideration for when changing the storage size, currently this is not documented.
2. Set the user to a useful value in the capacity metrics app, ideally something like storage mode conversion task but even Power BI Service as used for other internal operations would be better.
makromer
on:
Fabric Data Pipeline should be able to execute dbt...
on:
Customers should ereceive notifications for all th...
miguel
on:
Recent Data and Recent Connections