Write optimized DSO used to pull large volume of data
a. Used where fast loads are essential. Example: multiple loads per day (or) short source system access times (world wide system landscapes).
i) If the Data Source is not delta enabled. In this case, you would want to have a Write-Optimized DataStore to be the first stage in BI and then pull the Delta request to a cube.
ii) Write-optimized DataStore object is used as a temporary storage area for large sets of data when executing complex transformations for this data before it is written to the DataStore object. Subsequently, the data can be updated to further InfoProviders. You only have to create the complex transformations once for all incoming data.
b. Write-optimized DataStore objects can be the staging layer for saving data. Business rules are only applied when the data is updated to additional InfoProviders.
c. If you want to retain history at request level. In this case you may not need to have PSA archive; instead you can use Write-Optimized DataStore.
d. If a multi dimensional analysis is not required and you want to have operational reports, you might want to use Write Optimized DataStore first, and then feed data into Standard Datastore.
e. Probably you can use it for preliminary landing space for your incoming data from diffrent sources.
f. If you want to report daily refresh data with out activation.In this case it can be used in reporting layer with InfoSet (or) MultiProvider.
Functionality of Write-Optimized DataStore
Only active data table (DSO key: request ID, Packet No, and Record No):
o No change log table and no activation queue.
o Size of the DataStore is maintainable.
o Technical key is unique.
o Every record has a new technical key, only inserts.
o Data is stored at request level like PSA table.
No SID generation:
o Reporting is possible(but you need make sure performance is optimized )
o BEx Reporting is switched off.
o Can be included in InfoSet or Multiprovider.
o Performence improvement during dataload.
Fully integrated in data flow:
o Used as data source and data target
o Export into info providers via request delta
Uniqueness of Data:
o Checkbox “Do not check Uniqueness of data”.
o If this indicator is set, the active table of the DataStore object could contain
several records with the same key.
Allows parallel load.
Can be included in Process chain with out activation step.
Supports Archiving.