Requirements and Limitations
- 4 minutes to read
- Supported OLAP Servers
- Data Provider Requirements and Limitations
- OLAP Mode Limitations
- OLAP Culture Settings
Supported OLAP Servers
The following OLAP servers are supported:
- Microsoft SQL Server 2000 Analysis Services
- Microsoft SQL Server 2005 Analysis Services
- Microsoft SQL Server 2008 Analysis Services
- Microsoft SQL Server 2008 R2 Analysis Services
- Microsoft SQL Server 2012 Analysis Services (Multi-dimensional mode)
- Microsoft SQL Server 2014 Analysis Services (Multi-dimensional mode)
- Microsoft SQL Server 2016 Analysis Services (Multi-dimensional mode)
- Microsoft SQL Server Analysis Services 2008 requires Microsoft SQL Server 2008 Service Pack 1.
- Microsoft SQL Server Analysis Services 2005 requires Microsoft SQL Server 2005 Service Pack 2.
- Microsoft SQL Server Analysis Services 2000 requires SP4.
- In Microsoft SQL Server Analysis Services 2000, the ASPxPivotGrid does not support a cube's dimension members with DBNull values.
Data Provider Requirements and Limitations
To use the OLE DB and ADOMD.NET providers, the ASPxPivotGrid requires the Microsoft Analysis Services OLE DB and Microsoft ADOMD.NET providers on the web server. Refer to the Data providers used for Analysis Services connections document for more information.
The following limitations are in effect when you use OLE DB and ADOMD.NET providers:
- The application should run in Single-Threaded Apartment (STA) mode if the OLE DB data provider is used to establish a connection to the Microsoft SQL Server 2000 Analysis Services.
- When binding to local cubes, use either an OLE DB or ADOMD.NET provider. When one provider has established a connection, the other provider becomes unavailable in the scope of the current process. There is a common situation that results in an exception: an attempt to connect to a local cube using OLE DB provider followed by disconnection and another attempt to connect to the same cube (or another cube file in the same process) using ADOMD.NET provider.
OLAP Mode Limitations
The following features have limitations in OLAP mode:
- You should handle the ASPxPivotGrid.CustomServerModeSort event to apply Custom Sorting;
- The PivotGridFieldBase.DisplayFolder property used to manage User Folders does not allow you to edit the dimension root folders. However, you can specify the PivotGridFieldBase.OLAPExpression, PivotGridFieldBase.OLAPDimensionCaption and PivotGridFieldBase.DisplayFolder properties for the newly created field to place it in the OLAP field tree displayed in the Customization form.
The following Pivot Grid features are not supported in OLAP mode:
- Custom Summaries;
- Custom Totals whose summary type is set to Custom;
- Grouping Intervals;
- the Grouping - this form enables end users to build complex filter criteria (see WebPrefilter);
- Filtering by Summaries;
- the Others field value (see PivotGridFieldBase.TopValueShowOthers);
- the PivotGridFieldBase.SummaryType cannot be changed;
- Sorting by Summaries is not supported if Custom Totals are displayed;
- creating two or more fields bound to the same data source field (except for data fields bound to the same measure if they have different PivotGridFieldBase.SummaryDisplayType values);
- adding fields bound to cube measures to any area except the data area;
- adding fields bound to cube dimensions to the data area.
- Unbound Fields are not supported, but you can create a new field, specify its PivotGridFieldBase.OLAPExpression property and use it in place of an unbound field.
OLAP Culture Settings
When the ADOMD.NET data provider (specified via the PivotGridControl.OLAPDataProvider property) connects to an OLAP data source, the provider requests the value and formatted text from the OLAP server's cube. This information includes a format string and the culture information.
If the OLAP server does not provide culture information, the client's culture settings are used to format the value (except currency settings). The client's culture settings are also used if you use the PivotGridFieldBase.CellFormat property to specify the format. To use different culture settings to format values, handle the ASPxPivotGrid.CustomCellDisplayText event.