|Oracle9i OLAP Developer's Guide to the OLAP DML
Release 2 (9.2)
Part Number A95298-01
Basic Concepts, 3 of 6
The following are some situations in which you might use the OLAP DML:
The most common types of calculations that the OLAP DML is used for include:
In addition, the OLAP DML can be used when you want to perform calculations that are not easily accomplished in the ETL process or by using the OLAP API.
You can commit data to the analytic workspace without committing it to SQL tables. This is very useful for work in process. For example, you might have a forecasting application where you want to allow users to save personal forecasts and reuse them during a later session, but you do not want users to commit the forecast to the SQL tables.
To use the OLAP DML, you:
After you use the OLAP DML to analyze data, you can then:
You can create an analytic workspace with a command such as the following:
This command creates a new and empty analytic workspace named
For more information about creating an analytic workspace, refer to Chapter 2, "Defining and Working with Analytic Workspaces".
To use the OLAP DML, data must exist in the analytic workspace. Data can be loaded into an analytic workspace from SQL tables or from flat files. In most cases, tables within the database will be the data source. To load data into the analytic workspace, you use commands in the OLAP DML.
Analytic workspaces can be either temporary or persistent, depending on your needs. If the analytic workspace is needed only to perform a specific calculation and the results of the calculation do not need to be persisted in the workspace, the workspace can be discarded at the end of the session. This might occur if, for example, your application needs to forecast a small amount of sales data. Since the forecast can be rerun at any time, there might not be any point in persisting the results.
Analytic workspaces can also be persisted across sessions. You might want to persist data in the analytic workspace if you have calculated a significant amount of data (for example, a large forecast or the results of solving a model), or if you have aggregated data using non-additive aggregation methods.
Data in analytic workspaces may be shared by many different users. To share data in an analytic workspace, the workspace needs to be persisted during the period of time it is to be shared.
For example, if you want to allow a user to share the results of a forecast, you can allow the user to persist the analytic workspace. If another user attaches that workspace during their application session, they can be allowed to see the other user's forecast.