Importing a database into SQL Elastic Pool is taking longer than expected

PS 376 Reputation points
2023-08-25T17:41:01.5233333+00:00

Hi All,

I am currently working on a POC and attempting to import a 300mb DB into SQL Elastic Pools. While the process initially started fine, it has been over 14 hours and it's still not complete. Can anyone provide any insights into why it may be taking this long or suggest a way to identify the root cause of the issue?

Thank you in advance.

Azure SQL Database
{count} votes

1 answer

Sort by: Most helpful
  1. Rahul Randive 8,176 Reputation points Microsoft Employee
    2023-08-26T02:59:26.45+00:00

    Hi PS

    To make the process relatively faster, you can import the database first and then add it to the elastic pool if you want to manage the resources and performance of the database more effectively.

    Additionally, while importing the database, you can select a relatively higher pricing tier to get more compute. Once the database is imported, you can downscale it.

    User's image

    To answer your other question, what causes delays in the process?

    The Azure SQL Database Import/Export service provides a limited number of compute virtual machines (VMs) per region to process import and export operations. The compute VMs are hosted per region to make sure that the import or export avoids cross-region bandwidth delays and charges. If too many requests are made at the same time in the same region, significant delays can occur in processing the operations. The time that's required to complete requests can vary from a few seconds to many hours.

    Hope this helps!

    Thank you