Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!

Reply
DingbatData
Advocate I
Advocate I

Informix Database issue and parallel loading of tables in the service

I am connecting to an Informix (IBM) database as our client is using IBM Pronto. We started off building the report in the PBI Desktop and it worked fine when connecting to a single table, but when all data was refreshing, the Informix Database would crash. Client would have to phone someone to get it restarted. So not good.

So, I disabled parallel loading of tables and this fixed the issue. I can now refresh all the data in PBI Desktop without crashing Informix. So that is good. However, after publishing to the service, refreshes from the service cause Informix to crash again.  Again, not good and we really need to automate daily refreshes of the data.

After reading this post:

https://community.powerbi.com/t5/Service/Disable-parallel-loading-of-tables-in-web-published-report/...

(which is quoted below)

Q: "Is there a setting for a web published PBI report that will disable parallel loading of tables?"

A:  "No, you can only setup this option on power bi desktop site. Power bi service use different methods to handle different connection mode, so it may faced the issue to use parallel mode to handle mixed mode."

It seems like you cannot disable parallel loading of tables in the service. Does anyone have any suggestions for me?

1 ACCEPTED SOLUTION
v-xicai
Community Support
Community Support

Hi @DingbatData ,

 

It is not supported to disable parallel loading of tables in the Power BI Service currently .There is an idea about this issue, please vote it up, Need option to disable Parallel loading of tables in PBI Service , to improve the Power BI.

 

It is a place for customers provide feedback about Microsoft Office products . What’s more, if a feedback is high voted there by other customers, it will be promising that Microsoft Product Team will take it into consideration when designing the next version in the future.

 

We also submitted this feedback to the product group internally, so that the product group can pay attention to this problem and speed up the issue repairing.

 

When the refresh is in fact slow or crash, it can be due to several reasons:

  • Insufficient CPU (refresh can be very CPU-intensive).
  • Insufficient memory, resulting in refresh pausing (which requires the refresh to start over when conditions are favorable to recommence).
  • Non-capacity reasons, including data source system responsiveness, network latency, invalid permissions or gateway throughput. You may increase the capacity for workspaces to increase the model refresh parallelism frequency.
  • Data volume - a good reason to configure incremental refresh, Incremental refresh can significantly reduce data refresh duration, especially for large model tables. See more: Incremental refresh in Power BI Premium .

 

See more details: https://docs.microsoft.com/en-us/power-bi/whitepaper-powerbi-premium-deployment#why-are-refreshes-sl....

 

You can also use some tips to improve the performance:

 

   Enable Row-Level Security (RLS) where applicable.

   Use Microsoft AppSource certified custom visuals where applicable.

   Do not use hierarchical filters.

   Provide data categorization for Power BI reports (HBI, MBI, LBI).

   Use the On-premises data gateway instead of Personal Gateway.

   Use slicers sparingly.

   Remove unused tables or columns, where possible.

   For more information on optimizing data sources for DirectQuery, see DirectQuery in SQL Server 2016 Analysis Services.

 

You can refer to the links to see more performance tips:

https://docs.microsoft.com/en-us/power-bi/power-bi-reports-performance,

https://blog.pragmaticworks.com/power-bi-performance-tips-and-techniques,

https://maqsoftware.com/expertise/powerbi/power-bi-best-practices.

(Please understand that this link is provided “AS IS” with no warranties or guarantees of content changes, and confers no rights.

 

Best Regards,

Amy

 

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

2 REPLIES 2
v-xicai
Community Support
Community Support

Hi @DingbatData  ,

 

Does that make sense? If so, kindly mark my answer as a solution to help others having the similar issue and close the case. If not, let me know and I'll try to help you further.

 

Best regards

Amy

 

v-xicai
Community Support
Community Support

Hi @DingbatData ,

 

It is not supported to disable parallel loading of tables in the Power BI Service currently .There is an idea about this issue, please vote it up, Need option to disable Parallel loading of tables in PBI Service , to improve the Power BI.

 

It is a place for customers provide feedback about Microsoft Office products . What’s more, if a feedback is high voted there by other customers, it will be promising that Microsoft Product Team will take it into consideration when designing the next version in the future.

 

We also submitted this feedback to the product group internally, so that the product group can pay attention to this problem and speed up the issue repairing.

 

When the refresh is in fact slow or crash, it can be due to several reasons:

  • Insufficient CPU (refresh can be very CPU-intensive).
  • Insufficient memory, resulting in refresh pausing (which requires the refresh to start over when conditions are favorable to recommence).
  • Non-capacity reasons, including data source system responsiveness, network latency, invalid permissions or gateway throughput. You may increase the capacity for workspaces to increase the model refresh parallelism frequency.
  • Data volume - a good reason to configure incremental refresh, Incremental refresh can significantly reduce data refresh duration, especially for large model tables. See more: Incremental refresh in Power BI Premium .

 

See more details: https://docs.microsoft.com/en-us/power-bi/whitepaper-powerbi-premium-deployment#why-are-refreshes-sl....

 

You can also use some tips to improve the performance:

 

   Enable Row-Level Security (RLS) where applicable.

   Use Microsoft AppSource certified custom visuals where applicable.

   Do not use hierarchical filters.

   Provide data categorization for Power BI reports (HBI, MBI, LBI).

   Use the On-premises data gateway instead of Personal Gateway.

   Use slicers sparingly.

   Remove unused tables or columns, where possible.

   For more information on optimizing data sources for DirectQuery, see DirectQuery in SQL Server 2016 Analysis Services.

 

You can refer to the links to see more performance tips:

https://docs.microsoft.com/en-us/power-bi/power-bi-reports-performance,

https://blog.pragmaticworks.com/power-bi-performance-tips-and-techniques,

https://maqsoftware.com/expertise/powerbi/power-bi-best-practices.

(Please understand that this link is provided “AS IS” with no warranties or guarantees of content changes, and confers no rights.

 

Best Regards,

Amy

 

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Helpful resources

Announcements
April AMA free

Microsoft Fabric AMA Livestream

Join us Tuesday, April 09, 9:00 – 10:00 AM PST for a live, expert-led Q&A session on all things Microsoft Fabric!

March Fabric Community Update

Fabric Community Update - March 2024

Find out what's new and trending in the Fabric Community.

Top Solution Authors
Top Kudoed Authors