LOADMEMBER

Metaoutline

The name of the metaoutline—case-sensitive. This metaoutline is used to extract data and create an Essbase outline.

Essbase Application

The name of the Essbase application on the target Essbase Server computer where the Essbase outline is created.

Essbase Database

The name of the Essbase database on the target Essbase Server computer. Integration Server applies this name to the Essbase outline.

Member Load Filter ID

Optional. You can specify a member load filter ID to use when loading members. If you do not specify a filter ID, the default name (*DEFAULT) is used. The default filter ID is 1; any additional filters are numbered sequentially, starting with the number 2. For information about creating filters, see the Integration Services Console Help.

Delete and Restore Database

Optional. The Delete and Restore Database parameter directs whether Integration Server should delete all members in the Essbase database before performing a member load. The default is N (No).

This is the format:

DELETE_DB=[Y|N]

When this option is selected (DELETE_DB=Y), the options Delete All Members First, Modify Essbase Users, and Incremental Update cannot be used.

Values are as follows:

Y Delete and restore (re-create) theEssbase database during the member load process.

N Do not delete and restore the Essbase database (this is the default).

Delete All Members First

Optional. When the Delete All Members First parameter is selected (OTL_CLEAR=Y), Integration Server removes all members from the existing database and then re-creates the database by using the members in the metaoutline.

This process is slower than creating or updating an Essbase outline without deleting the members; therefore, do not delete all members first unless it is necessary. You should delete all members if, for example, you know that some members have been removed from the OLAP metaoutline and you want to build an Essbase outline containing a smaller set of members. The default is N (No).

This is the format:

OTL_CLEAR=[Y|N]

Values are as follows:

Y Remove all members from the existing database and then re-create the database by using the members in the metaoutline.

N Do not remove members from the existing database; only update the Essbase database (this is the default).

DimID-MbrID, DimID-MbrID,... DimID-MbrID

Optional. Incremental Upate. The level at which dimensions are updated during an incremental member load. The format is:

INCUPD=DimID-MbrID,DimID-MbrID,...DimID-MbrID;[;]

Values for incremental update are as follows:

Dynamic Restructuring Member Load Options

Optional. Specify 1, 2, 3, or 4. Dynamic restructuring member load options set the parameters for restructuring the database during a member load. The option that you select affects any subsequent data loads.

Values are as follows:

1 Preserve all data. Select to preserve all existing data that applies to the changed outline when restructuring occurs. This is the default (INCUPD_MEMBER=1).

2 Discard all data. Select to clear all data from the database.

3 Preserve level 0 data. Select to preserve data only for level zero members.

This is the optimal restructure option if you change the source database and need to recalculate the data, and if all data required for the calculation is in level zero members.

Selecting this option deletes all upper-level blocks before restructuring. This reduces the disk space for restructuring and improves calculation time when the database is recalculated. The upper-level blocks are re-created when you calculate the database.

4 Preserve input data. Select to preserve only those blocks containing data that is loaded. Many applications contain data that is entered at parent levels. Selecting this option prevents deletion of any blocks that are created by data load, whether they are non-level zero or level zero (leaf member) blocks.

Attribute Update Level

Optional. Use with the Incremental Update parameter. The level at which attribute dimensions are updated when a member load is performed. Values are as follows:

0 Delete all attribute dimensions after the member load is performed.

1 Do not update existing attribute dimensions while updating other types of dimensions (for example: standard, time, or measures dimensions) during a member load.

2 Update all existing attribute dimensions and add new attribute dimensions during a member load.

Username List

Optional. Lists all user IDs that can access the Essbase application and database into which you are loading the members. Commas separate user IDs. For example, @@USERS="admin","ljones","ksmith".

Esscmd Script File

Optional. The name of an ESSCMD script. The script that you define instructs Essbase to perform specified actions on the Essbase database. These actions might include changing a member tag or loading data from a worksheet into user-defined members after you load the data from the data source. The ESSCMD script must be in the eis/server/esscript directory.

Create Unicode Application

Optional. You can specify that a Unicode application is created on Essbase Server. The default is that no Unicode application is created.

This parameter cannot be overwritten. For example, if a previous application exists and you are overwriting that application with the current member load, you cannot overwrite the original Unicode or non-Unicode setting.

This is the format:

UNICODE=[Y|N]

For example:

UNICODE=Y

Update Drill-Through Data Only

Optional. Update drill-through information or hybrid analysis information.

There is no separate option for hybrid analysis. Use this command for both drill-through information and hybrid analysis information.

This is the format:

UPDATE_DTDATA_ONLY=[Y|N]

For example:

UPDATE_DTDATA_ONLY=Y