Re: [PERFORM] Stored procedures

2006-01-20 Thread Rikard Pavelic



Hi,
 
Will simple queries such as SELECT * FROM blah_table WHERE tag='x'; 
work any

faster by putting them into a stored procedure?




IMHO no, why do you think so? You can use PREPARE instead, if you have 
many

selects like this.



I tought that creating stored procedures in database means
storing it's execution plan (well, actually storing it like a
compiled object). Well, that's what I've learned couple a years
ago in colledge ;)

What are the advantages of parsing SP functions every time it's called?

My position is that preparing stored procedures for execution solves
more problems, that it creates.
And the most important one to be optimizing access to queries from 
multiple connections (which is one of the most important reasons for 
using stored procedures in the first place).


Best regards,
   Rikard



---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
  subscribe-nomail command to [EMAIL PROTECTED] so that your
  message can get through to the mailing list cleanly


Re: [PERFORM] Stored Procedures

2006-01-19 Thread Andreas Kretschmer
Benjamin Arai [EMAIL PROTECTED] schrieb:

 Hi,
  
 Will simple queries such as SELECT * FROM blah_table WHERE tag='x'; work any
 faster by putting them into a stored procedure?

IMHO no, why do you think so? You can use PREPARE instead, if you have many
selects like this.


HTH, Andreas
-- 
Really, I'm not out to destroy Microsoft. That will just be a completely
unintentional side effect.  (Linus Torvalds)
If I was god, I would recompile penguin with --enable-fly.(unknow)
Kaufbach, Saxony, Germany, Europe.  N 51.05082°, E 13.56889°

---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings