Note You may experience the same problem when you use the Automated Export preview feature to perform an export operation.
Azure SQL Database Import/Export ServiceThis problem occurs when many customers make an import or export request at the same time in the same region.
The Azure SQL Database Import/Export Service provides a limited number of Compute virtual machines (VMs) per region to process the import and export operations. The Compute VM is 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 occur in processing the operations. The time that is required to complete requests can vary from a few seconds to many hours.
Note If a request is not processed within 12 hours, the service automatically cancels the request.
Automated Export preview featureThis problem occurs because the Automated Export preview feature in the Microsoft Azure portal uses the Azure SQL Database Import/Export Service to perform automated exports.
The Automated Export feature first makes a database copy of your original database to make sure that the export is consistent transactionally. Then, the Automated Export service queues an export of the database copy by using the Microsoft Azure SQL Database Import/Export REST service API. Therefore, the Automated Export preview feature can also take a long time to perform an export because it relies on the Azure SQL Import/Export Service to perform the export operation.
After the export is complete, the database copy is deleted. Notice that because Automated Export makes a database copy before the export operation, you will incur additional database charges for the database copy. Databases are billed daily. For example, a daily export of a database incurs an additional charge for the database copy on every day. This effectively doubles the cost of your database.
Although Microsoft continuously works to improve the Azure SQL Database Import/Export Service, the performance of the service varies because of the reasons that are mentioned in the "Cause" section. If your application requires consistently faster or more predictable import or export performance, you can perform the BACPAC import or export directly in your code by using the DACFx API. The DACFx API is a set of classes that you can use to perform operations on a BACPAC package. This lets you write your own BACPAC utility application or include BACPAC functionality in any application.
To obtain the DACFx API libraries, you can download the latest version of Microsoft SQL Server Data-Tier Application Framework.
If your database exports are used only for recovery from accidental data deletion, the Basic, Standard, and Premium editions of SQL Server all provide self-service restoration capability from system-generated backups. You do not have to pay for the backups, and the backups are transactionally consistent without your having to perform the automated export. This reduces your overall cost.
Article ID: 2965554 - Last Review: 16 Jun 2014 - Revision: 1