Eksportuj (0) Drukuj
Rozwiń wszystko
Ta zawartość nie jest dostępna w wymaganym języku. Wersja w języku angielskim znajduje się tutaj.

Report execution timeout (Azure SQL Reporting)

Updated: May 9, 2014

SQL Reporting will discontinue service on October 31, 2014. See this FAQ for details. For reporting on Microsoft Azure, visit Virtual Machines on WindowsAzure.com.

Windows Azure SQL Reporting imposes a report execution time-out as mitigation against potential denial of service attacks, and as a technique for maintaining service health and availability.

Report execution time-out is 3 minutes and 45 seconds, per report execution. The time-out interval begins when the report request is received by the service. It ends when the report is rendered. As such, the report execution time-out must be sufficient to accommodate data retrieval, processing, and rendering. By placing SQL Database and SQL Reporting in the same data center, you can reduce latency for data retrieval.

This setting is imposed by the SQL Reporting gateway service, which manages external connections to a SQL Reporting service. This setting is fixed for all reports, for all tenant subscribers, across all editions and subscription plans. It is based on the Azure Load Balancer time-out of 4 minutes, with approximately 15 seconds dedicated for SQL Reporting gateway processing. Because the time-out is dependent on the load balancer time-out, you cannot change the Report Execution either in the portal, or programmatically in application code.

For reports that contain subreports, report execution is calculated independently for each embedded report contained within a larger report.

The on-premises server, Reporting Services (SSRS), has a query execution time-out that is separate from report execution time-out. Query execution time-out refers to the maximum amount of time allowed to retrieve data from an on-premises database. The query execution time-out is set on the data source connection, and as such, must fall inside the report execution interval.

SQL Reporting neither exposes nor uses this setting. The query execution time-out is built-into the report execution time-out. You cannot set a query execution time-out property for report data sources that run on SQL Database.

See Also

© 2014 Microsoft