Known limitations in creating AS2000 local cubes
CubeSlice allows you to create local cubes that have most of the functionality of server cubes. Listed here are the known limitations. Some of these are limitations of the local cube technology provided by Microsoft and some are limitations caused by the design of the CubeSlice.
There are some limitations that only apply when using one of the two forms of the cube creation syntax. See Local cube and global cube creation syntax for a description of these limitations.
We are always working to add new functionality. We will inform all current users and trial users when new versions are available.
Virtual dimensions created with SQL Server 7.0
You cannot use virtual dimensions created with OLAP Services in SQL Server 7.0. If you are using Analysis Services in SQL Server 2000, you may be using some cubes that were created with SQL Server 7.0 OLAP Services and this limitation will apply to those virtual dimensions.
Cubes with disabled levels
You cannot create a local cube from a source cube that has any disabled levels. This is true even if you exclude the dimension containing the disabled level.
The creation of local cubes from source cubes that have invisible levels is fully supported.
Slicing on members with illegal characters
You may not be able to slice (filter) on members that have the following characters in the member names:
\ / : ; * ? " < > |
HideMemberIf property
The Level property HideMemberIf is used to create ragged dimensions. It is not supported at all when using the Global Cube Syntax. When using Local Cube Syntax it is supported for the following options:
It is not supported for the these options:
Slicing on many members
You may receive an out of memory error message or an internal error message when you slice (filter) on too many members in one cube. We have successfully sliced on 100 members from one dimension and 50 members from a combination of dimensions.
Large cubes
You may have problems when creating very large local cubes. The cubes may take a long time to create and the cubes may be slow to browse. We have used CubeSlice to successfully create local cube files of up to 500 MB, but we usually try to limit the size of our local cubes to 50 MB. Some OLAP client applications may be able to browse larger local cubes than others.
Distinct Count limitation
You can include measures with Distinct Count aggregation in your cube only if certain requirements are met. Please see Measures with Discount Count Aggregation for more information.
Source cubes cannot have disabled levels
You cannot create a cube from an Analysis Services cube that has a disabled level in any of its dimensions.
Virtual cubes and member properties
You cannot include any member properties in a virtual cube if that virtual cube also has measures included which are in one source cube but not in one of the other source cubes.
Analysis Services functionality that is not included in local cubes
The following features of your Analysis Services cubes are not included in local cubes you create: