SAS

Moving OLAP Cubes (Part 1 – It’s all between the schemas)

by  •  • Comments Off on Moving OLAP Cubes (Part 1 – It’s all between the schemas)

This post was kindly contributed by real business intelligence for real users - go there to comment and to read the full post.

SAS recommends building OLAP Cubes on a separate ‘non-production schemas’ because cube building can be resource intensive and time consuming. Each OLAP Server can be defined to one & only schema at a given time, therefore you will need to setup the architecture to include another OLAP Server & Schema outside of the typical installation.

To save cube building time, you can also change the OLAP Schema a cube is associated to without rebuilding the cube structure. (Of course, the cube physical file structure must be accessible to both OLAP Server instances.) Included is one way to move the OLAP Cubes:
  1. When OLAP Cubes are initially developed select the OLAP Schema created for development/testing.
  2. When you are ready to move the OLAP cube to production, you will first need to ‘disable’ the cube via OLAP Cube Studio: 
  3. Then the administrator will select ‘Maintain’ -> ‘Change OLAP Schema’ and click the Production OLAP Server Schema. 

This post was kindly contributed by real business intelligence for real users - go there to comment and to read the full post.