Power Bi Premium

Thank you, can this be ?

Create two parameters in the power query on desktop and activate the incremental one based on this

https://learn.microsoft.com/en-us/power-bi/connect-data/incremental-refresh-overview#create-parameters:~:text=Power%20BI%20Premium.-,Create%20parameters,-To%20configure%20incremental

Regardless of the capacity you can only deploy desktop files smaller than 1GB. You could use a powerquery parameter to filter the report, for deployment, then remove it in the service. You could also use incremental refresh to reduce your file size, so you can deploy. The Semantic Model can then grow beyond 1GB in the service

Thank you for replying

Right now what I have activated is an update in this way

Based on what he tells me, I don't understand how he could solve the problem

Thank you

Right now, I'm in the phase of updating the report from Service and it's taking me a long time, in fact yesterday I put it to load and I reject it because it was a very heavy moelo.

Hora de inicio
23/3/2025, 17:49:19
Hora de finalización
24/3/2025, 6:48:55
Duración
—
Tipo de actualización
A petición
Capacity
Reserved Capacity for Pro Workspaces
Puerta de enlace
No Gateway
Error
La operación de actualización falló porque tardó demasiado en completarse. Considere reducir el tamaño de su conjunto de datos o dividirlo en conjuntos de datos más pequeños.

Hi Syndicate_Admin ,

Thank you for reaching out to Microsoft Fabric Community.

Thank you Deku for the prompt response.

For the error you are facing "the dataset is too large to refresh due to timeout or memory issues" - often caused by complex models or large imported tables.

Here are some Troubleshooting steps to solve the issue:

1.Check your workspace is truly in Premium capacity:

Go to your workspace settings

Ensure the “Premium capacity” toggle is ON, and it's assigned to a dedicated capacity (like P1/P2)

2.Optimize your model:

Remove unused columns or tables

Reduce cardinality (e.g., long text fields, high-distinct columns)

Consider changing large tables to DirectQuery or Hybrid Tables

3.Split large data loads:

Use incremental refresh on large fact tables to avoid full dataset loads every time

Break up complex queries in Power Query

4.Use XMLA endpoint to check dataset size:

If you're in Premium, you can use tools like Tabular Editor or SSMS to connect via XMLA and get detailed metrics

• If everything looks right but the problem continues, contact Microsoft support with the Cluster URI and Activity ID you shared - that will help them trace it.

If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it! 

Thank you.

Hi Syndicate_Admin ,

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

Hi Syndicate_Admin ,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.

Thank you.

Hi Syndicate_Admin ,

I hope this information is helpful. Please let me know if you have any further questions or if you'd like to discuss this further. If this answers your question, please accept it as a solution and give it a 'Kudos' so other community members with similar problems can find a solution faster.

Thank you.