object type

[dba_admin]

I am writing stored procedures to process our data. One of the requirement is to get the highest score from a list of vendors. In procdure A, I will evaluate the vendors by looking at their credit scores, capicacity and some other creteria. Then, in procedure B, I will calculate some other score only for those vendors passing procedure A.

Currently, I am using "object type" to pass the list of vendors with their property (address, id number, nationality and etc ...). Users are complaining performance and the company is thinking of getting rid of "object type."

Question: Does any one of you have comment of using "object type" to process data like the one I just described? Do you have any other approcach to achieve the same goal without using objects? What's is the pro and con of using objects? Any performance impact?

[abhaysk]

Cant u Merge those 2 Procs as 1, rather then doin all circus by passing params?

[dba_admin]

Procedure A will be called by many other procedures. So, I have to seperate them.

[slimdave]

How did you trace the performance problem to the use of object types?

[dba_admin]

We are processing 50,000+ records weekly. After implementing object types, the batch process slow down, according to the users. This is acutally one of our client's case. I am trying to see if there is alternative of "Object Type".

What I am thinking is Object type is actually better than straight table query because it can load "the set" of frequently-processed data into the memory to expedite the process. The problem is when the number of records in the object table increase dratimatically, it become a memory burdon.