Power Bi Premium

[Syndicate_Admin]

Hello, good afternoon

I hope you can clarify this doubt for me

I have a Power BI Premium capacity and I have created a report and I have been using it for a long time and now it tells me that I can't because I go over 1 GB of storage in the dataset.

But by having Premium I have more than 1GB of storage

Has anyone found a similar case?

Thanks a lot

[v-venuppu]

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.

[v-venuppu]

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.

[v-venuppu]

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.

[v-venuppu]

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.

 

[Syndicate_Admin]

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.

[Syndicate_Admin]

I get this on the error screen

[Syndicate_Admin]

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-paramete...

[Deku]

Yes

[Syndicate_Admin]

Okay okay, I'm going to go step by step :
1. I've created two parameters

2. In the power query I have created a range from that date to the next

3. Now I've closed it and I've applied it and it takes me to the dashboard and this is where I have to publish it.

And now in Service what do I have to do ?

Should I do this whenever I want to repost?

Thanks a lot

[Deku]

You should have datetimes rather than date.

In power bi desktop you need to right click to create the incremental policy before you publish. On the first refresh in the service the partitions will be created and you will pull in data as per your incremental window

[Syndicate_Admin]

The Date column comes in DD/MM/YYYY format from the source. What should I do then?
On the other hand, when I do all this that I have to do, it is published to the service but what would I have to do if I want to download the .pbxi format since I have seen that it cannot be done.

Thanks a lot

[Deku]

You need to keep the desktop version you push to the serviced saved somewhere. 

Please see this blog post on downloading, undownloadable reports and models.

[Deku]

RangeStart and RangeEnd should be datetime but you can convert to date in the powerquery query with DateTime.Date

[Syndicate_Admin]

The model is already loaded with today's data and applied and closed, now I am in the dashbaord directly and I do not find in the tables (all of them are put together in encargosanx) that I have created the range start filter and range end the "incremental update" button.
Could it be that I have to do this in the ?

[Deku]

In power bi desktop you right click on the table in the report view and will be able to open the this window to define the policy

[Syndicate_Admin]

I've come up with this for each table, published it to service, and I'm going to reload the app again from Service.
And from there it would already be working daily once you set the automatic upload again, right?
Thanks a lot

[Deku]

Should be. Once refreshed you can use SQL server management studio to check all your partitions have been created

[Syndicate_Admin]

Yes, how could I do it?
Thanks a lot

[Syndicate_Admin]

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

[Deku]

You filter the data in the report to get it below 1gb.

If you follow the guide for incremental refresh you can filter locally to a single day of data. When you publish and refresh in the service, partitions will be made for the table, for the range of dates you've specificed for the incremental load window. The service will take the RangeStart and RangeEnd parameter and fill each partition with data beyond that single day, you specified locally. This then grow up to the size of the limits for your specific capacity