Requirements and Limitations

Mar 14, 2021
3 minutes to read

Supported OLAP Servers

The following OLAP servers are supported.

Microsoft SQL Server 2000 Analysis Services (requires SP4)
Microsoft SQL Server 2005 Analysis Services (requires Microsoft SQL Server 2005 Service Pack 2)
Microsoft SQL Server 2008 Analysis Services (requires Microsoft SQL Server 2008 Service Pack 1)
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)

Note

In MS SQL Server Analysis Services 2000, the PivotGridControl 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 PivotGridControl requires the Microsoft Analysis Services OLE DB and Microsoft ADOMD.NET providers on the client machine. 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 PivotGridControl.CustomServerModeSort event to apply Custom Sorting;
the PivotGridField.DisplayFolder property used to manage User Folders does not allow you to edit the dimension root folders. However, you can specify the OLAPExpression, OLAPDimensionCaption and DisplayFolder properties for the newly created field to place it in the OLAP field tree displayed in the Field List.

The following Pivot Grid Control features are not supported in an OLAP mode:

Custom Summaries;
Custom Totals whose SummaryType is set to Custom;
Grouping
Building complex filter criteria using the Filter Editor;
The Others field value (see Display Top N Values);
Sorting by Summaries is not supported if Custom Totals are displayed;
Creating two or more fields that refer to the same datasource field (except for data fields, which can refer to the same measure if they have different PivotGridField.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 OLAPExpression property and use it in place of an unbound field.

OLAP Culture Settings

When the ADOMD.NET data provider (specified using the OlapDataProvider property) connects to an OLAP data source, the provider requests the value and formatted text from the cube. The measure format received from the server includes a format string and the culture information.

Note

If OLAP server does not provide culture information, the client culture settings are applied to format the measure value, except the currency settings. If you explicitly specify the format using the CellFormat property, the measure value will be formatted using the client’s culture settings. To format values using different culture settings, handle the CustomCellDisplayText event.