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

Be one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now

Reply
sara_sameer
Frequent Visitor

Power BI Report Server scheduled Refreshes

Hello, I have published three reports in my report server that are from the same database. Therefore I have one refresh scheduled plan and apply it on three of them I want to understand the concept how is it actually working when im creating one schedule for three different reports but same database is the refresh starting once only and be impleneted on the three of them or when one report is done from refreshing its moving to the other one?
And also, what if I create other refresh schedules for each one of these reports how the process will be?
The idea is im trying to see which method will take less time to refresh so i can make the schedules to refresh every less than one hour maybe. And I've noticed that when having different schedule for each of these report even tho they have the same starting time one of the report is refreshing but the other is still waiting not refreshing at all.
I need the best recommendations, thank you.

1 ACCEPTED SOLUTION
hackcrr
Super User
Super User

Hi, @sara_sameer 

To optimize the refresh process and reduce the total time required, consider the following recommendations:
Ensure that your report server and database server have sufficient resources (CPU, memory, I/O capacity) to handle multiple concurrent refresh operations. Monitor performance during refreshes to identify any bottlenecks.
Stagger refresh times: Instead of scheduling all reports to refresh at the same time, stagger refreshes by a few minutes. This reduces the likelihood of resource contention and helps ensure a smoother operation. For example: schedule Report 1 to refresh at 12:00, Report 2 at 12:02, and Report 3 at 12:04.
If a sequential refresh is acceptable, use a single schedule:
If sequential refresh times (refreshing reports one by one) are acceptable, using a single schedule simplifies administration and avoids server overload.
Optimize report queries: Ensure that queries used in reports are optimized for performance. Efficient queries reduce the time required to refresh each report. Consider indexing, query optimization and ensure that the database design supports efficient data retrieval.
Monitor and tune: Continuously monitor refresh performance and tune as needed. Use server logs, performance counters and database monitoring tools to gather insights.
Consider load balancing: If you have multiple reporting servers or load balancing setups, distribute refresh tasks between servers to improve performance.

 

hackcrr

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

View solution in original post

2 REPLIES 2
sara_sameer
Frequent Visitor

Hello @hackcrr, thank you for your reply it was helpful!

 

hackcrr
Super User
Super User

Hi, @sara_sameer 

To optimize the refresh process and reduce the total time required, consider the following recommendations:
Ensure that your report server and database server have sufficient resources (CPU, memory, I/O capacity) to handle multiple concurrent refresh operations. Monitor performance during refreshes to identify any bottlenecks.
Stagger refresh times: Instead of scheduling all reports to refresh at the same time, stagger refreshes by a few minutes. This reduces the likelihood of resource contention and helps ensure a smoother operation. For example: schedule Report 1 to refresh at 12:00, Report 2 at 12:02, and Report 3 at 12:04.
If a sequential refresh is acceptable, use a single schedule:
If sequential refresh times (refreshing reports one by one) are acceptable, using a single schedule simplifies administration and avoids server overload.
Optimize report queries: Ensure that queries used in reports are optimized for performance. Efficient queries reduce the time required to refresh each report. Consider indexing, query optimization and ensure that the database design supports efficient data retrieval.
Monitor and tune: Continuously monitor refresh performance and tune as needed. Use server logs, performance counters and database monitoring tools to gather insights.
Consider load balancing: If you have multiple reporting servers or load balancing setups, distribute refresh tasks between servers to improve performance.

 

hackcrr

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

Helpful resources

Announcements
Las Vegas 2025

Join us at the Microsoft Fabric Community Conference

March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!

Dec Fabric Community Survey

We want your feedback!

Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions.

ArunFabCon

Microsoft Fabric Community Conference 2025

Arun Ulag shares exciting details about the Microsoft Fabric Conference 2025, which will be held in Las Vegas, NV.

December 2024

A Year in Review - December 2024

Find out what content was popular in the Fabric community during 2024.