Data Monitoring / Power BI Performance & KPI Integrity
Power BI: DirectQuery source bottlenecks
A visual is slow because its generated source query scans too much data. Capture the generated query through supported diagnostics and inspect its source execution evidence.
Environment and inputs: Power BI semantic models and reports; measure behavior depends on relationships, storage mode and filter context.
Failure scenario
A visual is slow because its generated source query scans too much data. Confirm the cause before choosing a fix.
Evidence to collect
Capture the generated query through supported diagnostics and inspect its source execution evidence. Record the time, affected scope and a healthy comparison interval.
Fix the confirmed cause
Improve source filtering or modeling and validate that report results and source workload remain acceptable. Write the expected result first. Change one relevant setting at a time.
Check the result and hand over
Repeat the check for directquery source bottlenecks using the same scope and a representative interval. Check that the symptom is resolved, expected records are present and downstream results are correct. If coverage, correctness or latency worsens, restore the recorded configuration through the agreed rollback process.
Scope and precautions
Prefer read-only access and limit queries to the relevant period or dataset. This example has not been tested on your systems. Test changes in an approved environment. Keep credentials and sensitive data out of shared evidence.