Wow ... when I implemented pipelined functions, I didn't really care = much about what happens in SGA and PGA. I wanted to get data fast i.e. = as soon as available (as in select statements) and couldn't wait sitting = around for oracle to return ALL data at once (as it happens in = functions and procedures). My recommendation is 'to try it first' ... in your environment and then = see. If I mention any inefficiency, it may or may not happen in your = environment. In early versions of 9i, there were few bugs, but most were = resolved by 9202 ... but it is worth checking at Metalink. One thing you should watch out for is ... pipelined functions still have = an outstanding issue with cursor_sharing=3Dforce setting, they like it = to be EXACT and dislike FORCE for whatever reason. Try it out ... it is a nice feature. Raj -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of sushma manjunath Sent: Friday, April 09, 2004 7:27 AM To: oracle-l@xxxxxxxxxxxxx Subject: Re: Pipelined table Functions Is their some white paper or documentation that describes in detail how = a=20 table function affects a system, and what happens within the SGA / PGA = when=20 this process runs. I have read the docs on OTN and they explain pipeline = and=20 parallel but do not go into any down side for this function in an OLAP=20 environment. I am looking for some possible repercussions of this = function=20 in the way of resource, and performance issues that might arise. ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------