How does Power BI schedule refresh work when multiple reports use the same SQL tables and incrementa

Hi manoj_0911, 

If all the reports are using the exact same tables, you should make one semantic model and point all the reports at that same model, that way the data is only refreshed once. 

If each report has its own semantic model, and they are all set to refresh at the same time, they do refresh at the same time, potentially hitting the source system with the same queries 20 times. Depending on the size of your SQL Server instance, this could create a high load. 

1) Are all refreshes triggered at the same time?

Yes, potentially. Power BI Service uses a time window, not an exact queue. If you schedule 20 datasets for “every 2 hours”, many of them will start within the same few minutes.

2) Does Power BI queue or stagger them automatically?

Only partially, and only inside a capacity.

Power BI has two different throttling layers:

a) Capacity-level throttling (Fabric / Premium)

• Limits how many refreshes can run in parallel per capacity

• If the capacity is busy, some refreshes wait

b) Gateway-level throttling

• The on-prem gateway also limits concurrent queries

• But again, it’s generic — not table-aware

3) Will this overload SQL Server?

Common symptoms when many incremental refreshes collide:

• CPU spikes

• TempDB pressure

• Blocking (especially if ETL writes happen at the same time)

• Sessions getting killed (ties directly to your earlier SQL 596 issue)

• Refreshes randomly failing “sometimes but not always”

Incremental refresh reduces data volume, but:

• It still opens multiple SQL sessions

• Still scans partitions

• Still competes for locks, memory, and I/O