This article lists known issues that may occur when you use
Microsoft SQL Server 2005 Analysis Services cube-based report models in SQL
Server 2005 Report Builder.
Analysis Services and Report Builder are integrated in SQL
Server 2005. You can generate report models that are based on Analysis Services
cubes and use these report models in Report Builder. However, the following
known issues may occur:
- In Report Builder, when you select a report model that was
generated from an Analysis Services cube, you must select a perspective that is
contained within the model. You must not select the top-level model itself. If
your report contains items that are not within a single perspective, an error
may occur when you try to render the report.
- The number of entities and relationships of entities in a
navigation path are limited. The behavior in Report Builder is limited to the
Analysis Services equivalent of navigating from a dimension to a related
measure group and then to a second related dimension. In future versions of SQL
Server, the user interface (UI) will restrict the length of the navigation
path. In SQL Server June 2005 Community Technology Preview (CTP), the UI does
not restrict the length of the navigation path. Therefore, your report may fail
if the navigation path exceeds the limit.
- The parent-child attribute relationships are not visible in
- The sort order that is applied by Analysis Services is not
preserved by the reports. This issue is especially noticeable for time
attributes, such as the Month attribute.
For more information about how to create an Analysis
Services cube-based model, see the "How to Create a Model Using Report Manager"
topic in SQL Server 2005 Books Online.
For more information about SQL
Server 2005, visit the following Microsoft Web site: