Skip to Content
avatar image
Former Member

Data load takes long time in DSO when look up dso changes to write optimized type

Hi All,

We have a delta  load from DSO 1 to DSO2 picking 30k records .It has end routine which  does a look up on standard DSO (say DSO3).having 26 million records

The load DSO 1 to DSO2 takes few minutes to finish .But after changing the look up DSO3 to write optimized type, the load from DSO1 to DSO2 taking more than 2 hours .

Can you please suggest why it takes much take after changing the dso type.

We changed to write optimized because standard dso takes long time for activation step.,

Regards

Pradeep

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • Best Answer
    avatar image
    Former Member
    Dec 30, 2014 at 04:41 PM

    You can have a key field in standard DSO but in case of wite optimized DSO there are technical key. They are Request GUID field (0REQUEST), the Data Package field (0DATAPAKID) and the Data Record Number field (0RECORD).

    Hence you can create semantic key on DOC NUMBER and sorting the key set and applying Binary search will suffice your problem.



    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Dec 30, 2014 at 04:26 PM

    Hi Pradeep,

    You need optimize your final routine, if your lookup have all key of ods3, there should be no problem, check your sort instruction and read. If you not have all keys, you need create a index in your ods3.

    Please share your code, maybe can help.

    Regards.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Pradeep,

      If you want decrease the time, you can create other standard DSO or a infoobject with your doc_number zparv and employee where your zparv in 'ZB' and 'KB'.

      Your can use this object in initial routine or your you can use read masterdata.

      I hope helps.

      Regards.

  • avatar image
    Former Member
    Dec 30, 2014 at 04:06 PM

    In case of standard DSO there is a concept of SID. All the data present in the Satndard DSO has a sid corresponding to every data in the DSO and hence look up is faster.

    In case of Write Optimized DSO there are no SID's concept. So look up involves actual values looked up. It is always recommended to have a standard DSO on top of a Write Optimized DSO.

    Refer Difference Between Standard DSO and Write Optimized DSO for more details.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      HI Raja,

      I think SID is for reporting purpose.Does SID support for look up as well?

      Regards

      Pradeep

  • Dec 30, 2014 at 04:16 PM

    Hi Pradeep

    The end routine for lookup on DSO containing 28 Mio records is certainly going to run long.

    Please try to optimize the lookup code by making precise selections in data read statement and try to create secondary indexes on write optimized DSO based on the fields you use for selections.

    This will improve data read time from WO DSO.

    However please mention the runtime of data load when you were trying to make a lookup on Standard DSO.

    Ashish

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Ashish,

      How to find runtime of data load when trying to make a lookup on Standard DSO.

      But the same look up code  takes less time when it was standard dso

      Regards

      Pradeep