gourak1

 Profile Answers by gourak1 

• Jun 30th, 2010

 

In incremental aggregation, Informatica saves the aggregate values at a temporary location on the server which it can increment to during the next load.  If you give sorted input in this case, the records come as presorted for that particular run but may not be in the perfect sort order if we take into account the already saved aggreagte values.  That is why this option is not allowed..

Hope it answers your question...

ahammed

 Profile Answers by ahammed 

• Jul 20th, 2010

 

When you are selecting sorted input the data will be sorted and at the same time last record key value will be stored in repository. After that days or months passing on some new records will be added. When you are selecting sorted input option it sort the records and last record key value is placed somewhere. When you are performing incremental agrigation it calculate new record summary based last key value. But key value is located somewhere. From there onwards it calculate the summary.

NOTE: Sorted input improve the performence and remove duplcates when you are 
selecting  sorted input option 
incremental agrigation calculation new records summary.

jayapraveen

 Profile Answers by jayapraveen 

• Oct 3rd, 2010

 

Because of the performance tunning, because here the duplication of the data is sorted in the bginining of the aggregation itself so index cache and data cache  is reduced so the performance is good.