Generally speaking, yes. The improvement in performance will depend on the level of complication of the query.... I've seen only a very slight performance gain for simple one-table SELECTs, but for more complicated queries, with complex execution plans, I have seen better improvement. In other words, in my experience, the more complicated the execution plan that SQL Server has to put together, the more umph you get from storing the SELECT as an sproc.
>I have a lot of queries that are built inside the vfp front end, very simple example here with how I call it:
>
>
>lcLastName='KELLY'
>text to lcCmd noshow
> select lastname, firstname, mi from coPatients where isactive=1
> where lastname=?lcLastName
>endtext
>
>if sqlexec(gnConnHandle,lcCmd,"CurPatLookUp")<1
> =sqlerror()
>else
> ...code here
>endif
>
>
>is there a performance difference if I make all my queries StoredProcedures vice just calling them in this fashion?
>
>Thanks
>Kirk
The whole problem with the world is that fools and fanatics are always so certain of themselves, but wiser people so full of doubts. - Bertrand Russell