Maa,
It is a great concept,,, store everything in memory and eliminate
disks. with enough memory you could store the info each user needed.
If the user is going to request the same info each time why not use
materialized views to increase the thru put.
Ron
>>> maryann_30@xxxxxxxxx 03/11/2004 1:16:21 PM >>>
We have a fairly big query that takes about 6 hours
to complete. To speed up things, we thought of the
following: Create a logon trigger, which stores in memory
each user's info during login time.
Then when the user clicks a button that starts this query,
to have his/her info already in memory as opposed to
getting it from disk somewhere.
So basically, I just wanted to verify that a login trigger
does indeed store things in memory and keeps it there
until logout. Is that correct, or should I expect surprises?
thanks,
maa
----------------------------------------------------------------
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
-----------------------------------------------------------------
----------------------------------------------------------------
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
-----------------------------------------------------------------
