This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(204.8, 20%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBG%3C/text%3E%3C/svg%3E)
Hey folks,
Is there any better way to scale up and down SQL azure databases quickly? This takes significant amount of time specifically when using standard pricing tier with DTU model and when databases are bit larger in size.
We know that there are tools, scripts or commands can do it but the issue is with the time taken to scale up and down such databases (even from azure portal). We are also aware that the time taken is directly proportional to the size of the database but looking for inputs if there is any better and faster way to do it.
Currently, this is making it almost impossible to write data processing pipelines that first scales up the databases before running their transformations and scale it down at the end.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(73.60000000000001, 21%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDB%3C/text%3E%3C/svg%3E)
Have you considered the Serverless Tier? https://learn.microsoft.com/en-us/azure/azure-sql/database/serverless-tier-overview
Yes tried it, however after evaluating our use case internally, the fixed dtu based tiers are the most relevant choice and hence looking for recommendations, if there are any.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(281.6, 93%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENS%3C/text%3E%3C/svg%3E)
@Bhushan Gawale
Please check this document on the dynamic scaling for the better understanding of the same. There will always be downtime associated with Scaling up and down and as you said that will depend on the size and SKU of the resources that you use.
Hope this helps.
Thanks
Navtej S
Yes, have taken a look at it and downtime could be fine and its almost minimal. The problem is that the amount of time taken to complete the scale up and down operation is significant when it comes to switching database DTU units of larger databases.
@Bhushan Gawale
Can you explain your use case in a better way. You are worried about the downtime which you say is minimal or you are worried even if the downtime is minimal it takes long time for actual scale up.
If that is the case I think there is no apparent solution to that. The Scaling up and down will definitely be dependent on the size of DB. What Azure aspire for is to ensure the downtime is minimal.
Please explain your question further for better understanding.
Thanks
Navtej S
Other than Serverless, the only other way to scale up and down a database quickly is to co-locate the databases on an Elastic Pool or Managed Instance and stagger their use of the shared Elastic Pool/MI resources.