SQL Azure Reporting Preview Release Notes

This Release Notes document is updated periodically and available only online. These release notes are carefully and closely monitored. Any changes you make will be evaluated and then quickly accepted, refined, or reverted. Because this is a wiki, additions or refinements to these release notes might have been made by community members.

This section of the Release Notes document applies to the following release:

SQL Azure Reporting Preview

Issue 1: The performance for SQL Azure Reporting is less than a comparable on-premise hardware deployment of SQL Server Reporting Services.

Resolution 1: There is no work-around for this issue in this SQL Azure Reporting Preview.

Issue 2: Reports that take more than one minute to render might not successfully complete. 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 Azure Reporting SOAP endpoint.

Resolution 2. Try filtering data in the dataset queries to retrieve less data or to simplify the report design.

Use optimized queries and limited size result sets. Understand approximately how much data will be returned at run-time. On a client that uses SQL Azure database as the backend, try writing query that returns the result set in about 30 seconds 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, then add detail rows. For charts, start with a pie chart, then try a bar chart with one series, then charts with multiple series.

Issue 3: The Atom feed document (.atomsvc) from a report cannot be used as a data source by Microsoft PowerPivot for Excel.

Resolution 3: There is no work-around for this issue in this SQL Azure Reporting Preview.

Issue 4: Report item images where the image source is a link to an external image is not supported.

Resolution 4: There is no work-around for this issue in this SQL Azure Reporting Preview.