Scaling elastic pool duration

Paul Beare 25 Reputation points
2023-06-13T16:51:41.7433333+00:00

We have an elastic pool with 30 databases, most are less than 50 GB. The pool is a 32 vcores, but during the evening/night we only need to maybe half this performance.

We can't have long periods of downtime, ideally we would like less than a 1 minute. To scale say from 32 cores down to 16 cores during the night and then back up to 32 in the morning.

What would be the estimated during for scaling down and up? We are using the general purpose tier.

Azure SQL Database
0 comments No comments
{count} vote

1 answer

Sort by: Most helpful
  1. Alberto Morillo 34,671 Reputation points MVP Volunteer Moderator
    2023-06-13T18:29:05.43+00:00

    If you are scaling up and down the vcores (elastic pools vcore model) then the process of scaling up and down is less than a minute, based on my experience with elastic pools of up to 1 TB.

    That is the greatest benefit I found on elastic pools how fast you can scale up and down. I know organizations that need to scale up on certain period of times during the day to handle expected spikes on demand and they do it on elastic pools with very low impact on their customers.

    For elastic pools based on eDTU then answer is a bit different and can be found here.

    1 person found this answer helpful.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.