Forum Discussion

StevenVDP's avatar
StevenVDP
Frequent Visitor
4 years ago
Solved

Long scheduled refresh wait with Pro

Hi there,   we currently have set up a scheduled refresh on a single dataset. The Import dataset resides in a Pro workspace and is connecting to Synapse Serverless with a SQL credential.   When l...
Need Help
  • Burningsuit's avatar
    Burningsuit
    4 years ago

    Hi StevenVDP 

    For what it's worth, I think you've identfied your problem. This is the "noisy neighbour" scenario and your Pro licence is probably waiting in a queue for its refresh. Especially if you find that moving to PPU speeds the process up (provided you have made no other changes) it seems clear that the culprit is the Pro licence.

    In this scenario I'd try changing the time of the refresh, to see of refreshing earlier or later in the day is faster. Moving refresh to 7:30am may actually get your data refresh done by 8:00am. But on the other hand - why worry ? provided the refresh gets done eventually, you can shift the timeings around to cope and there's no real problem.

    Hope this helps

    Stuart

Burningsuit's avatar
Burningsuit
Resident Rockstar
4 years ago

Hi StevenVDP 

For what it's worth, I think you've identfied your problem. This is the "noisy neighbour" scenario and your Pro licence is probably waiting in a queue for its refresh. Especially if you find that moving to PPU speeds the process up (provided you have made no other changes) it seems clear that the culprit is the Pro licence.

In this scenario I'd try changing the time of the refresh, to see of refreshing earlier or later in the day is faster. Moving refresh to 7:30am may actually get your data refresh done by 8:00am. But on the other hand - why worry ? provided the refresh gets done eventually, you can shift the timeings around to cope and there's no real problem.

Hope this helps

Stuart