Incorrect/outdated data shown by report

[Anonymous]

I have a very strage problem, which I cannot solve for 3 days.
I have a Direct query report, the data source is SQL server and query is very simple select * from qq, where qq is a view.
Here is the result I see online (pay attention to Status and start_time)

 Here is the desk top view

and here is the query result right from the server

As you can see the online result is outdated no matter now many time I refresh the report and semantic model.
What can it be?

[V-yubandi-msft]

Hi @Anonymous ,

Could you please confirm if your issue has been resolved or if you require any further information? If the issue is resolved, kindly mark it as the Accepted Solution to assist other members who may encounter similar issues.

[V-yubandi-msft]

hi @Anonymous ,

Could you let us know if your issue has been resolved or if you are still experiencing difficulties? Your feedback is valuable to the community and can help others facing similar problems.

Thank You.

[V-yubandi-msft]

Hi @Anonymous ,

Could you kindly confirm if your issue has been resolved or if you are still encountering any problems? Your feedback is valuable to the community as it assists others who might be facing a similar issue.

Regards,

Yugandhar.

[V-yubandi-msft]

Hi @Anonymous ,

You're on the right track. Thanks for sharing the details of your issue. It looks like there's a mismatch between the data shown in Power BI and what's actually in SQL Server, especially with the Status and start_time fields.

 Here’s a step-by-step approach to help troubleshoot and fix this.

• Even though we mentioned DirectQuery earlier, it's crucial to double-check it.
• Make sure both Power BI Service and SQL Server are set to UTC, and verify there are no time zone discrepancies.
• Head to Power BI and confirm that the refresh schedule is running smoothly without any delays.
• If you're using DirectQuery, confirm it's retrieving real-time data from SQL Server. If real-time updates aren't essential, consider switching to Import Mode for more consistency.
• In SQL Server, run the SELECT * FROM qq query directly to verify that the view returns the latest data.
• To remove outdated data, clear Power BI’s cache. If the issue persists, use the XMLA Endpoint to refresh it programmatically.
• Use SQL Profiler to capture and review T-SQL queries. Check if Power BI is sending the correct queries and whether the Status field updates as expected.
• Make sure there are no ongoing issues or outages affecting data refresh by checking Power BI Service Health.
• Ensure there are no RLS rules or permission issues restricting data visibility. Make sure the Power BI connection has the necessary access to SQL Server.
• In Power BI Desktop, enable Query Diagnostics to analyze how queries are executed and identify any potential inconsistencies.
• If the issue persists and real-time data isn't critical, switch to Import Mode for better data consistency and performance.

Thank you for your response @lbendlin .

If my response solved your query, please mark it as the Accepted solution to help others find it easily.

And if my answer was helpful, I'd really appreciate a 'Kudos'.

[Anonymous]

Is this AI generated response? 

[V-yubandi-msft · Accepted solution]

Hi @Anonymous ,

We would like to clarify that the troubleshooting steps provided are based on best practices and real-world scenarios observed in similar cases. Additionally, some steps have been referenced from official Microsoft documentation. For your convenience, we have attached snapshots and reference links.

References:
Data refresh in Power BI - Power BI | Microsoft Learn

DirectQuery in Power BI - Power BI | Microsoft Learn 

Our goal is to provide you with practical solutions and the most effective troubleshooting steps based on similar issues and best practices. Rest assured, this solution is not AI-generated but comes from our experience and trusted sources.

Regards,

Yugandhar.

[V-yubandi-msft]

Hi @Anonymous ,

Thank you for your feedback and for confirming that both Power BI Service and SQL Server are running on UTC. We understand your concern about the mismatch where the Status shows Running in SQL Server but Succeeded in Power BI Service, even after multiple refresh attempts using Direct Query.

The troubleshooting steps provided are based on best practices and real-world scenarios observed in similar cases.

If you need further clarification on the suggested steps or additional approaches, please let me know.

Regards,

Yugandhar.

[Anonymous]

Is there a way to ban user here or to report spam?

[lbendlin]

yes. you should have at least the "report inappropriate content" link

[Anonymous]

Even more strage stuff

I catched the T-SQL  sent by PBI while I'm refreshing the reports via sql profiler, and even that stmt is returning "Running" valule for Status field.

[lbendlin]

Power BI Service runs on UTC.  Which timezone is your SQL server running on?

[Anonymous]

UTC as well, the biggest problem is the status - It is Running, but Online shows it as Succeeded.