PL/SQL tables chomp up the PGA for your session (you'll eventually get an ORA-4030). Theoretically this has no effect on anyone's session but your own, but of course, if you've just consumed a great bucketload of server resources, then other people *will* be impacted... On many occasions, when we want to a row-by-row operation and map it into plsql tables for performance, the real cause of the problem is the row-by-row approach. Trying to do things in sets (either with straight SQL or bulk-collect etc) is typically a better approach than massive plsql tables in memory. hth -- Connor McDonald =========================== email: connor_mcdonald@xxxxxxxxx web: http://www.oracledba.co.uk "Semper in excremento, sole profundum qui variat" -- //www.freelists.org/webpage/oracle-l