Partitioning can be managed by either the database server or the MicroStrategy application. Either way, tables are partitioned at the database level. The terms “application” and “server” refer to what manages the partitioned tables, not where the tables are split.
The database server, rather than MicroStrategy, manages the partitioned tables in RDBMS server-level partitioning. The original fact table is not physically broken into smaller tables. Instead, the database server logically partitions the table according to parameters specified by the database administrator. You do not need to take any action in MicroStrategy to support the partitioning.
Since only the logical table is displayed to the end user, the partitioning is transparent to MicroStrategy. In contrast, in application-level partitioning the relational database is unaware of the partitioned tables.
Refer to your database documentation for details on server partitioning for your particular platform.
In application-level partitioning the application, rather than the RDBMS server, manages the partition tables. A partition base table (PBT) is a warehouse table that contains one part of a larger set of data. Partition tables are usually divided along logical lines, such as time or geography. MicroStrategy supports two types of partitioning:
|•||Metadata partition mapping—stores the mapping information in the project metadata|
|•||Warehouse partition mapping—uses a specialized warehouse table to determine which table to access|