Forum Discussion
Slow initial load
Hi,
I have the same issue over here, since PBI Desktop august 2020 release.
It has always worked fine since 201706 untill 20208.
My reports use a Direct Query connection to an Azure SQL database.
Since the latest PBI Desktop update of June 2021 things are getting somewhat better however the problem is in the Service.
I clear the cache of my browser and then open my report.
Every single initial page load (page or drillthrough) has some lag.
After I've opened all the pages, I close the browser en reopen it, clear the cache and do the same navigation.
Than all works fine, I tested it with other filters so that the queries executed on the Azure SQL db are different.
It's a strange behaviour.
In januari I had a call with Simon Didier and he mentioned the following:
"After a data model is upgraded to the new metadata format,
AS will have the M Engine request the native/folded query for legacy DQ sources at runtime
instead of the native query being cached in the data model from PBI Desktop.
Requesting the native query at runtime is slightly different than how PBI Desktop does it,
which can result in a successful conversion in PBI Desktop and a failure in the Service.
The reason for this is due to a technically incorrect configuration in PBI Desktop -
we should be setting the ThrowOnFoldingFailure flag in order to match the Service.
Setting the flag will have queries fail to fold in Desktop as well."
Like I said the behaviour is better since june 2021 update but not 100%.
Thanks in advance
Frank
- collinq5 years ago
Super User
Hi Goofr ,
Are you using a Gateway? There is an update to help with Azure SQL outages which might be affecting you as well. (june 2021 Gateway Update)
- Goofr5 years ago
Advocate IV
Hello,
I'm not using a gateway because my data lives in the cloud (Azure SQL database).
I think it has something to do with cold and hot model. When the model is loaded then initially it's execution time on the database is slow because the queries aren't being stored in cache.
When the model is loaded in memory and the queries are executed everything works fine until the model is offloaded.The thing is: it doesn't work the way it used to work.
Frank