Forum Discussion
Dataset Refresh Timeout with SQL server
Do a comparison of resources between the Server and your local desktop. Do you have more resources on your local desktop and thus you get a better outcome?
Have you tried increasing the timeout amount using:
CommandTimeout=#duration(0, 0, 30, 0)
(my example is a 30 minute timeout)
Hi there
I think the problem lies elsewhere though, because in the week of the 18th to 22nd our dataset was refreshing on schedule, within minutes. And while our dataset does increase on a daily basis, there wasn't a rapid increase of data overnight to have led to the dataset timing out after an hour of trying to refresh.
What we've also experienced now, is that trying to refresh the dataset locally on the PBI app and publishing, is also causing a time out after +- an hour of publishing (with the error message "You do not have access to publish to this workspace" - which I do). Looking at our report though, it was in fact published/refreshed, but the error message appears to be due to a timeout on the app.
As for server resources, we have upped our resources to a higher tier, but it yields the same result: when the dataset is refreshing, our memory usage (according to the graphs) will go up to max, remain constant for a while and then suddenly drop and start to spike rapidly until timing out after an hour or so. I believe it is with this spiking in memory usage that leads to the refresh failing.
I guess my question remains: are there common causes for a dataset, that was refreshing normally at a time, to suddenly time out when trying to refresh?
Short answer to your question is no.
Why something timesout will entirely depend on what has changed in your dataset and what import logic complexity you are using. I mention resources as it might show you a point of difference and give you an idea if your server simply reached a limit before your desktop did.