Hi When you update a cube in place, you add data and new members directly to an active cube, without disabling, stopping, or rebuilding the cube. During and after the completion of the in-place update, existing sessions will continue to run on the old cube. When the last session ends on the old cube, the old cube is closed. After the old cube is closed, new sessions apply to the new cube. While existing sessions are connected to the old cube, new sessions are also applied to the old cube. If you do not want to wait for all open sessions to close, you can enforce a switch to the new cube. To switch to the new cube, disable the cube, close all open sessions that query that cube, and enable the cube. The in-place cube update runs like an incremental cube update. At the end of the in-place update, the cube metadata is updated to point to the new generation folder and the old generation folder is deleted. If the old generation cannot be deleted, because an existing session has locked the files, then the next cube update will attempt to delete the old generation folder. Deleting cubes Cube deletion takes place in PROC OLAP and SAS OLAP Cube Studio. If you delete cubes, that have not been updated, then the deletion operation removes cube metadata and physical files. For cubes that have undergone either in place or incremental update, the deletion of old versions and generation folders occurs programmatically. Manual file deletion is not required. For cubes that have undergone in-place updates, the next in-place update will remove all old generation folders. For cubes that have received incremental updates, deletion of metadata and physical files takes place as part of the coalesce process. Cheers Sanjeeva reddy Sanjeevareddie@gmail.com +91 9739133388
... View more
