write optimized, direct , standard dso

[Former Member]

hi,

     plz tell me in which scenario we will use write optimized dso, direct dso, standard dso??? and the exact difference between all of the 

note:don't tell that standard have 3 tables,direct and write op are having 1 table

[Former Member]

Hi Venkatesh,

Standard DSO

• Mailny useful for delta management as detail history of record is maintained in Changelog table using 0RECORDMODE.
• SIDs are generated only after activation, hence data is available for reporting after activation only.
• Data records with same key are aggregated
• Reporting possible and data stored in detail level.

WDSO

•   This supports faster data loading compared to Standard DSO. Hence these DSOs are used as staging layers. Further loading will be from these DSOs applying business logics.
• As it has only once table (Active data table ), activation is not required separately. Hence saves time in loading and data availability for data marting / reporting.
• SIDs will be generated after loading. Hence data is available for reporting soon after loading.
• Data records with same key are not aggregated

Direct DSO

• As Venkatesh and Aravind said, this is used for APD analysis and BAPIs are required for loading.
• SIDs cannot be generated.
• Data records with same key are not aggregated in this too

Have a look at this which gives you more details and scenarios where these are used

Hope this clears your doubt regarding DSOs

http://help.sap.com/saphelp_nw04s/helpdata/en/F9/45503C242B4A67E10000000A114084/content.htm

Regards

Chandu

[Former Member]

Hi Chandra,

Write optimized DSO Use in BEx Queries

For performance reasons, SID values are not created for the characteristics that are loaded. The data is still available for BEx queries. However, in comparison to standard DataStore objects, you can expect slightly worse performance because the SID values have to be created during reporting.

If you want to use write-optimized DataStore objects in BEx queries, we recommend that they have a semantic key and that you run a check to ensure that the data is unique. In this case, the write-optimized DataStore object behaves like a standard DataStore object. If the DataStore object does not have these properties, you may experience unexpected results when the data is aggregated in the query.

Regards,

Aravind.