the CREATE PROCEDURE/FUNCTION/PACKAGE/TRIGGER statement). The first time
you call an Oracle Stored Procedure it is loaded into Oracle's memory
(shared pool of the SGA). The stored procedure will stay there until it is
paged out (to make room for other stored procedures). Once the procedure
has been loaded into memory, it will execute quickly and the copy in memory
will be used for subsequent calls. There are some things that can be done
by the DBA to keep stored procedures in memory (pinning).
In Oracle, execution plans are usually associated with SQL statements not
with Stored Procedures.
I am not sure how stored procedures and execution plans are used in other
database environments or how the term compile is defined for those
environments.
Janet
>At 07:43 AM 8/26/2004 -0400, you wrote:
>>Can you really say that for Oracle? Point out any material on the net
>>that talks about it?
>>
>>I'm actually curious about this. So if you have any links that talk
>>further about this that would be great.
>>
>>Ian
>>
>>----- Original Message -----
>>From: Micha Schopman <[EMAIL PROTECTED]>
>>Date: Thu, 26 Aug 2004 12:53:28 +0200
>>Subject: RE: stored procedures
>>To: CF-Talk <[EMAIL PROTECTED]>
>>
>>Stored procedures are NOT pre-compiled. This is a common made mistake.
>>Only the execution plan gets cached, but the stored procedure is
>>compiled upon execution.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
