Troubleshoot Auto-scale History Graph Issues

Troubleshoot Auto-scale History Graph Issues

When attempting to view the auto-scale history, the following error may appear:

This is because the SQL database used by Nerdio Manager is set to a size that is insufficient for the scale of the AVD environment.

For example, this is an instance where the SQL server is undersized.

  1. The pricing tier is set to the default size of S1.

  2. The CPU graph shows consistent spikes to 100%, and remaining at 100% for a short duration. The DTUs allocated to the SQL server are not providing enough processing power, which means the queries do not finish before timing out.

  3. The maximum value across the last hour was 100%. Ideally, there should be no peaks above 95%. However, a very brief spike to 100% is not always an indicator of throttling.

By default, Nerdio Manager deploys with a pricing tier of S1, which is fine for most small to medium (less than 150 session hosts) environments. However, for larger environments, a larger database tier is often required for Nerdio Manager. Consider upgrading your SQL DTU quota from 20 to 100 or higher, depending on your environment.

To upgrade your SQL DTU quota:

  1. In the Azure portal, navigate to the SQL database overview. (As shown in the example above.)

  2. Select Pricing tier. (Shown as #1 in the example above.)

  3. Slide the DTUs slider to the desired size.

Was this article helpful?

0 out of 0 found this helpful
Have more questions? Submit a request

Comments (0 comments)

Please sign in to leave a comment.