Known Issues (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.|
This contains a list of known issues for SQL Reporting. The document will change over time as we remove items from the list, encounter new issues or learn more about existing ones.
File size limitation on Execution Log download
There is currently 1 MB file size constraint on the execution log file download. When attempting to download a file that exceeds the 1 MB limit, the following error occurs:
"Invoke operation 'GetExecutionLog' failed. Exception of type 'System.ServiceModel.DomainServices.Client.DomainOperationException' occurred. When you contact support, please provide the activity identifier and timestamp: <ActivityID> - <Timestamp>"
To work around this limitation, you can either restrict the date range so that less data is downloaded. Retention of execution log data is 60 days. Date ranges can be as little as 1 day."
Alternatively, you can file a support ticket with Microsoft Customer Support. You can file a ticket using either the Billing or Technical ticket type (Billing is the ticket type that appears when you are using the Trial version of Azure).
Upon request, Customer Support can provide execution log data at file sizes larger than 1 MB, yet still within the 60 day data retention period. To contact support, click your account name in the management portal and select Microsoft Customer Support from the drop-down menu. For more information about execution logs, see Download an Execution Log (Azure SQL Reporting)
Service and users must be provisioned manually
Currently, you must use the management portal to set up SQL Reporting as well as register report users. After the service and users are established, you can use the ReportServer2010 endpoint and SOAP API to assign roles, create folders, configure data sources, and deploy reports. For more information, see Report Server Web Service Methods. Additionally, review the following topic for information about unsupported API: Guidelines and Limitations for Azure SQL Reporting.
Folder hierarchy is limited to two levels
SQL Reporting is now integrated into the Azure management portal. In contrast with the previous portal, there is now a limitation in folder navigation to two levels: root level access, plus one additional folder.
For a new reporting service that you create in the portal, you will find that your folder hierarchy can only go two levels deep, supporting one layer of folders under the root node. For existing reporting services that were established previously, having a folder hierarchy with more than two levels, you can access reports and shared data sources using the report server HTML page:
Sign in to the management portal and select the SQL Reporting service.
Click the Web service URL on the Dashboard page to open the reporting service HTML page. You can click successive links to navigate a folder path. Folder navigation via the service URL is read-only. You can view items, but not edit or manage them.
SQL Reporting performance
The performance for Windows Azure SQL Reporting is often less than a comparable on-premise hardware deployment of Reporting Services. The following table lists known issues and possible solutions.
General tips for improving performance
Keep reports and data sources in same data center
Enable report caching. Although caching is turned off by default, developers can enable report caching programmatically to improve rendering times.
Reduce interactive height
Reports do not complete successfully
Reports that take more than four minutes to render might not complete successfully. This includes reports run from the report server by using the report URL and also reports that run programmatically when rendered by using calls to the SQL Reporting SOAP endpoint.
Optimize reports for the fastest possible rendering:
Use optimized queries and limited size result sets. Understand approximately how much data will be returned at run-time. On a client that uses Microsoft Azure SQL Database as the backend, try writing query that returns the result set in about 2 minutes or less. Queries that return large binary objects, such as images, might execute slowly due to bandwidth limitations.
Simplify the report design. For tables, start with a single table with one row group, then one row group and one column group, and then add detail rows. For charts, start with a pie chart, and then try a bar chart with one series, then charts with multiple series.
Report sorting issues with respect to the backend database
If you try to sort a table on a column for a report deployed to Windows Azure SQL Reporting, it might not sort in the order specified.
This happens because Microsoft Azure SQL Database does not allow setting the collation at the server level, and the report uses the default Windows collation setting. For more information about the collation support in Azure SQL Database, see SQL Server Collation Support (http://go.microsoft.com/fwlink/?LinkId=238699).
To resolve this issue set the collation property of the dataset in the RDL file. For more information about the collation property of a dataset, see DataSet.Collation (http://go.microsoft.com/fwlink/?LinkId=238700).
Report printing issues
When printing a report you might receive the following messages:
"Unable to load client print control"
“This website wants to install the following add-on: ‘SQL Server Reporting Services 2011’ from ‘Microsoft Corporation”.
To enable printing of SQL Reporting Reports, perform the following steps:
Click the print icon in the report ribbon.
In the "Unable to load client print control" window, click OK.
In the “This website wants to install the following add-on: ‘SQL Server Reporting Services 2011’ from ‘Microsoft Corporation’.” window, click Install.
Click the print icon again.
When prompted by User Access Control to allow changes to the computer, click Yes.
Select your printer and click OK.