On Thu, 2 Dec 2004 09:52:50 +0100, Stephane Faroult <sfaroult@xxxxxxxxxxxx> wrote: >=20 > Frank, >=20 > IMHO it is a bad idea to try, in whichever way, to improve on the way S= YS > objects work. If Oracle cannot properly take care of its own data, then t= he > situation is hopeless. I would rather say that the thing to check is the > deepreason behind those calls. >=20 > 1) SELECT SYSDATE FROM DUAL : is it useful? Why not use SYSDATE directly = in > the INSERT or UPDATE statements? Is the time component of the date really > useful in your application? Otherwise I guess that the initialisation > secti=E0on of a package, assuming of course that sessions don't stay conn= ected > overnight, could do. If I recall correctly; until recently (maybe 9.2) using SYSDATE directly in triggers etc (maybe all PL/SQL) generated 'select sysdate from dual' recursively. That is you could have large numbers of such calls without actually having coded them yourself. --=20 Niall Litchfield Oracle DBA http://www.niall.litchfield.dial.pipex.com -- //www.freelists.org/webpage/oracle-l