When changing Azure Sql Db tier (using azure dev ops pipelines) with bicep templates, is the maxSizeBytes property ignored?

Ryan Press 21 Reputation points Microsoft Employee

When changing from GP to Hyperscale, is it necessary to set a maxSizeBytes, as the default of Hyperscale is to scale to a maximum size of 100TB storage?

When creating a db in the portal with Hyperscale tier and viewing the ARM template, the maxSizeBytes is specified as 0. If you specify the maxSizeBytes as 0 in your bicep, it will be deployed and the ARM template of the resource will now read -1. If you re-deploy with any other value, the maxSizeBytes will not be revised.

Is this property being ignored by Resource Manager? In which case, should we include it, remove it when chaning tier, set it to 0 or set to 109951162777600?

Anyone have experience with this?

Azure SQL Database
{count} votes

Accepted answer
  1. GeethaThatipatri-MSFT 29,012 Reputation points Microsoft Employee

    @Ryan Press On reproducing the issue,100TB is the supported limit of hyperscale tier however, it is not a hard limit/max limit. Specifying a maxsizeBytes as 0 or 109951162777600 or any number in between does not make a difference for hyperscale tier as resource manager ignores it and this parameter is not available in portal for Hyperscale tier. If we change this value in ARM template, maxSizeBytes will always be -1 if you export the template of a hyperscale DB. As of now, this value is relevant for GP or BC tiers as these tiers have a hard limit of 4 TB and a lower limit could be set for management purposes, etc.

    Please let me know if you have any additional questions.

    Please don't forget to click on 130616-image.png or upvote 130671-image.png button whenever the information provided helps you. Original posters help the community find answers faster by identifying the correct answer.

0 additional answers

Sort by: Most helpful