Maintenance Windows on AAS
As with other hosted services, uptime and predictability are crucial for our users. We need to have a way of knowing when the server will be brought down for maintenance so we can schedule processing around it and notify our users well in advance.
The best way would be to implement maintenance windows, like SQL DWH, but a short-term fix could be to implement notifications BEFORE server downtime.
Two times in the last week, our automated nightly processing has been interrupted by "Server upgrade/restart". As this is a long-running processing and it is interrupted at the tail-end of the process, we need to re-do the full processing, meaning that it is not finished before the users need the service.
Full error details that we receive:
One or more errors occurred. Microsoft.AnalysisServices.Core: An error has occurred while trying to locate a long running XMLA request. The request might have been interrupted by service upgrade or server restart.
Jacob, Prinson commented
This has been occurring multiple times times under our production subscription since it has been procured in Azure and its interrupting our refresh operations even after implementing the incremental refresh and reduced the refresh window to 1hr to avoid these interruptions, now this has occurred twice in 10days, and both the time this failed our refresh operation, we would like to have a fix or planned module which can be controlled at the subscribers end.
Steve Coleman commented
In line with this request, if MSFT can post somewhere on the portal what updates were pushed out and when? We had a failure in the beginning of December when our models were no longer able to refresh due to invalid, but unused, M query code. Our only assumption is that an update was pushed out to AAS but since there is no posting of the update we can only assume this was the case.
Any update on this issue?
Same issue, frustrated
Hitting same issue second time in a month.