Managing OLAP Cube Data

Exporting and Importing Cubes

Cubes are exported and imported as part of a SAS package. SAS Management Console is one of the user interfaces that can perform the import and export of packages. For more information about creating SAS packages, see "Overview of the Promotion Tools" in the SAS Intelligence Platform: System Administration Guide.

The data administrator impact of exporting and importing cubes is that when cubes are imported, the tables used in the cube must be available and that building the aggregations for the cube is computationally intensive. The following list highlights some best practices:

It is impractical to package the detail tables and summary data for large cubes. Do not export them in the package.
If the cube is being imported to a new metadata server (as opposed to being moved to a new folder on the same metadata server) then make sure the same data sources for the detail tables used by the original cube are available and registered. Accomplish this by registering the same data servers and data libraries on the destination metadata server. If the cube uses a drill-through table, ensure that the library is pre-assigned.
When importing the cubes, be prepared to associate the cube with an OLAP schema. Consider that the OLAP schema determines the group of cubes that an OLAP server can access.
Once the cube is imported, the cube and its job are registered in metadata with relationships to an OLAP schema, tables, and folders. By default, the aggregations for the cube must be built after the cube is imported. Due to the computational intensity, consider rebuilding the cube during a period of low activity.

Top of Page