Power BI Desktop

Hi MLBLom,

This issue is expected behavior due to the 1 GB dataset size limit in Power BI Pro workspaces. Since your dataset is 1029 MB, it slightly exceeds the allowed limit, which is why the publish is failing.

Key Points:

• Power BI Pro / F2 capacity → Max dataset size: 1 GB
• Your dataset: 1029 MB → exceeds limit

Answers to your questions:

1. Will upgrading to F4 (or higher) resolve this?
   Yes. Moving to a higher Microsoft Fabric capacity like F4 or above increases the dataset size limits (typically up to several GBs depending on capacity). This alone can allow your PBIX to be published successfully.
2. Is capacity upgrade alone sufficient?
   Short answer: Yes, but not always optimal.

• Yes – upgrading capacity will allow publishing larger PBIX files.
• However, for datasets already crossing 1 GB, it’s strongly recommended to optimize the model or adopt a better architecture, because:
• Larger datasets impact refresh performance
• Memory pressure can affect capacity performance
• Scaling costs increase over time
  
  

Recommended Best Practices:

Instead of relying only on capacity upgrade, consider:

1. Optimize your dataset

• Remove unused columns
• Reduce cardinality (avoid high-cardinality text fields)
• Use aggregations where possible
• Disable auto date/time
  
  

1. Use Direct Lake / OneLake architecture

• Store data in OneLake
• Use Direct Lake mode to avoid importing large datasets into memory
  
  

1. Switch to DirectQuery (if applicable)

• Keeps dataset small but may impact performance depending on source
  
  

1. Incremental Refresh

• Only refresh recent data instead of full dataset
  
  

1. Composite models

• Combine Import + DirectQuery strategically
  
  

Recommendation:

If this is a quick fix → Upgrade to F4
If this is a long-term solution → Combine capacity upgrade + model optimization or Direct Lake approach

Hope this helps!
Kudos are appreciated if you find this useful, and feel free to mark it as the accepted solution.