Comments on: Notes on Fabric F2 Performance: Report Load https://prologika.com/notes-on-fabric-f2-performance-report-load/ Business Intelligence Consulting and Training in Atlanta Thu, 23 May 2024 13:11:19 +0000 hourly 1 https://wordpress.org/?v=7.1.2 By: Prologika https://prologika.com/notes-on-fabric-f2-performance-report-load/#comment-883 Thu, 23 May 2024 13:11:19 +0000 https://prologika.com/?p=9091#comment-883 In reply to Frederick Samson.

I don’t see a reason why not. It’s a good approach to reduce licensing cost if Fabric lakehouse or DW are appealing to you. Instead of shared, PPU licensing can also be used for semantic models and reports if you need more capacity and premium features.

]]> By: Frederick Samson https://prologika.com/notes-on-fabric-f2-performance-report-load/#comment-850 Thu, 23 May 2024 12:23:49 +0000 https://prologika.com/?p=9091#comment-850 Thanks for the article. As every report consumer need a Power BI Pro licence when < F64, would it be better to put all Fabric items on Fabric capacity except for Power BI semantic models and reports? Power BI content would be served using Pro/Shared Capacity which have great performance. So the Fabric capacity would be used for Ingestion/Transformatio (ETL) and would trigger a semantic model refresh (hosted on a Pro/Shared Capacity workspace). Afterwards, the Fabric capacity could be paused until the next refresh. We would lose the ability to use Deployments Pipelines for Power BI content but it would bring performance advantages. I would be interested in your opinion on this matter. Frederick

]]>