-
Hi,
Here I am thinking about one problem which is not clear to me, I have a package with 100 procedures, but no procedure is callig the ther procedure internally. Then what I am feeling is that, if three end users are connected to the database, and three queried for the same or the different procedures which are in that package. Then the entire pacaage is loaded into memory per each call of the end user? Or once it is loaded into the SGA , it will be available to all requests?
The main thing is is is good to keep those many procedures in a package when one is independent of other, or it is better to create each and every procedure individually?
Please provide me any thing related links for these tuning concepts.
regards,
khaleel
-
keep the package in shared pool is enough, once it's pinned in memory it can be call by all users without reparsing
-
You have to group your procedures into a package/s
according to its functionalities. In that way minimal
resources will be consumed in your shared pool(library cache).
I am sure each user needs separate task or set of functions.
But if you have more than enough resources, then why not
put it in one package.
