470,614 Members | 1,386 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 470,614 developers. It's quick & easy.

strategies for optimising common lookups etc

Hi all, apologies if this is a dumb question - not really sure where to look
for this kind of stuff...

I have a frequently called stored procedure that needs to access some
"configuration" information to determine how it should behave.

Currently I have the configuration information in its own table, and the sp
does a lookup "select item from config where pk = ...".

I am wondering whether there is any way to "cache" the result of a lookup
across instances of the stored procedure call? The configuration value will
rarely change, and as the procedure is called often it seems a bit of a waste
of resources looking it up each time the procedure is run.

Is this the sort of thing that internal variables would handle (by that I mean
using "set" and "show")?


Martin Hart
Arnclan Limited
53 Union Street
Dunstable, Beds
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?


Nov 11 '05 #1
0 1069

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

2 posts views Thread by robin | last post: by
4 posts views Thread by Jon Maz | last post: by
13 posts views Thread by CoreyWhite | last post: by
24 posts views Thread by David | last post: by
reply views Thread by origami.takarana | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.