When updating cubes
that have added syntax for a user written formatted search path or
SAS code, you must consider how that information will be updated as
well. Here are some possible scenarios.
Formatted Search Path Scenarios
|
|
|
You perform an update
in-place and do not make any changes to the format search path or
SAS source code.
|
The metadata for the
cube does not need to be updated. When the update runs, the current
format search path and SAS source code must be submitted with the
code.
|
You perform an update
in-place and change the format search path or the SAS source code.
|
The new values for the
format search path and SAS source code will be updated in the metadata
for the cube in addition to being submitted with the code or saved
with the exported code.
|
You create a new cube
in the update and do not make any changes to the format search path
or the SAS source code.
|
The new generation of
the cube will be created using the same format search path and SAS
source code as the original cube, and its metadata should also include
the same format search path and SAS source as the original cube.
The submitted code or exported code will contain the current format
search path and SAS source code. PROC OLAP will copy the current format
search path and SAS source code to the new cube as part of the update.
|
You create a new cube
in the update and enter a new format search path or new SAS source
code.
|
The next generation
of the cube will be created with the new format search path and SAS
source code, and its metadata will include the new format search path
and SAS source code. The submitted or exported code will contain the
new format search path and new SAS source code. However, PROC OLAP
will copy what is currently in the metadata for the original cube.
|