InvalidMaxSizeTierCombination error while performing scaling up operation

This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.

Worked on a service request where the customer was getting an error InvalidMaxSizeTierCombination while performing the scaling up operation.

 

Basically, the customer was trying to scale up the storage of his Azure SQL database from 500 GB to 1TB in the premium p6 tier.

The customer was reported below error message

Status message:

{

    'status': 'Failed',

    'error': {

        'code': 'InvalidMaxSizeTierCombination',

        'message': 'The tier 'Premium' does not support the database max size '1073741824000'.'

    }

}

 

Here is the things happened.

When I tried using the PowerShell with the same max limit value, I got a similar error.

As per the calculation instead of 1024000*1024*1024=1073741824000, we have to give 1099511627776

 

Example-

1TB

1 * 1024 GB

1 * 1024 * 1024 - MB

1 * 1024 * 1024 * 1024 - KB

1 * 1024 * 1024 * 1024 * 1024 – Bytes

 

  • If we convert this 1073741824000 bytes value to GB’s it will be 1000 GB. We have to provide values on those ranges only. P6 (1 , 2 , 5, 10 , 20 , 30 , 40 , 50 , 100 , 150 , 200 , 250 , 300 , 400 , 500, 750 , 1024) GB
  • We can perform using the portal and PowerShell also using the below command.

 

Set-AzSqlDatabase -ResourceGroupName "<rgname>" -DatabaseName "<dbname>" -ServerName "<servername>" -Edition "premium" -RequestedServiceObjectiveName "P6" -MaxSizeBytes 1099511627776

 

PowerShell snippet for reference

 

rahulrandive_0-1639816646189.png

Happy learning!

 

REMEMBER: these articles are REPUBLISHED. Your best bet to get a reply is to follow the link at the top of the post to the ORIGINAL post! BUT you're more than welcome to start discussions here:

This site uses Akismet to reduce spam. Learn how your comment data is processed.