Issue with azure SQL mi storage scale

Question

Issue with azure SQL mi storage scale

Riahi Mohamed 30

The azure SQL mi storage scaling process is taking too much time and sometimes it can take several days .is it a known bug ? Is there any best practice to perform this task ? Is there any possibility that it can be related to vnet custom dns configuration? Thank you

SSingh-MSFT 16,461 Reputation points Moderator

2024-04-10T04:14:02.1033333+00:00

Hi Mohamed RIAHI •,

We haven't heard back from you. In case you already found a solution, would you please share it here with the community? Otherwise, let us know and we will continue to engage with you on the issue.

Thanks

1 answer

Your answer

SSingh-MSFT 16,461 Reputation points Moderator

2024-04-10T04:14:02.1033333+00:00

Hi Mohamed RIAHI •,

We haven't heard back from you. In case you already found a solution, would you please share it here with the community? Otherwise, let us know and we will continue to engage with you on the issue.

Thanks

Answer 1

RahulRandive 10,501 Volunteer Moderator

Hi Mohamed RIAHI,

As per the Microsoft Document User's image Initiating a scale up, or scale down action, in any of the flavors mentioned above, restarts the database engine process, and moves it to a different virtual machine if needed. Once the target database engine is ready to process queries, open connections to the current database engine will be terminated, and uncommitted transactions will be rolled back and if you have long running queries, the scaling operation likely to take time.

Thank You!

Riahi Mohamed 30 Reputation points

2024-04-11T10:16:36.5433333+00:00

hi @Rahul Randive , thank you for your feeddback , is there any possiblity that the custom dns configuration on SQL MI vnet level can impact scale operations .

Share via

Issue with azure SQL mi storage scale

1 answer

Your answer