Write Optimized DSO

[Former Member]

Hello,

I have write optimized DSO and itsoverwriting.

In this DSO there is check mark for 'Do Not Check Uniqueness of Data', i know by doing this it checks for the uniqueness of the records based on the fields avaialble in techinical keys and the active table has multiple records with same key fields available in semaintic keys.

If i remove this check mark it will check the uniqueness of the record and if the data in fields which are avalable in the semaintic keys are same it will says duplicate entires.

My question is ,is there any way in the write optimized DSO that if we get same data for the fields availabe in the semantic keys then the DSO will overwite.

Cheers,

Vikram.

[Former Member]

The question is answered.

You should desgin your semaintic keys properly

[Former Member]

you've just found the biggest design considerationwhen using write opimised (no overwrite). I have all my write optimised DSOs feed a standard DSO so I can create delta records to subsequent targets.

I only use the write optimised DSO's for the Inbound Data Layer to store a record of the data from the source system.

cheers,

Rich

[Former Member]

Hi Vikram,

Write Optimised is purely for staging , in order to save activiation time.

In your case semantic key should be designed properly, if data is duplicated this semantic key gets violated and data will not load.

If you check the flag all the duplicate data will be sitting in the DSO.

you can allow this flag by keeping a standard dso over this dso and in the above dso it will overwrite the duplicate data .

Or if you dont check you must ensure that there is no duplicate information coming into write optimisied.

Thats why it is not recommended to create directly on write optimisied dso as there is no guarnatee of uniqueness of data.

Thanks

Vamsi

Edited by: vamsi talluri on Feb 14, 2011 5:50 PM

[Former Member]

Hi

Thanks vamsi, I just needed to have the conformation.

Cheers

Vikram