Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and a 50 percent discount on exams.
Get startedEarn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.
We created a new dataset that has 4 Import queries and one DirectQuery, all connected to SQL Server. The query that uses DirectQuery runs instantly in SSMS, but occassionally the visuals on our report will run for multiple minutes and either time out, or throw this error:
Initially we thought it was because we switched an existing report to point to this model after previously using a full import one, but we recreated the report from scratch and are still getting this error. We haven't used DirectQuery in any capacity beyond connecting to PBI datasets, so this is new to us. Our users definitely would prefer live data, but this is holding up an important project. Are there any settings we should be changing to prevent these errors?
@LaineyJB , There can be many reasons behind it.
Please share error in text format.
Any reason to shift to direct query mode? Import is the best way to work.
Hi @amitchandak, here is the text error:
Couldn't load the data for this visual
The service has encountered an error processing your request. Please try again. Error code 8632. A severe error occurred on the current command. The results, if any, should be discarded.. The exception was raised by the IDbCommand interface.
Without getting too detailed, basically an email with a link to our report is going to be sent to users when a certain trigger occurs. They would prefer that the data is immediately up-to-date corresponding with the trigger, as the actions to be taken based on the data are time-sensitive.