|
|
Posted by Chet on 05/25/07 07:19
"Adrienne Boswell" <arbpen@yahoo.com> wrote in message
news:Xns993B27D5D090arbpenyahoocom@69.28.186.121...
> Gazing into my crystal ball I observed "Chet"
> <cfnews@REMOVEcharter.net>
> writing in news:el%4i.23$As5.3@newsfe12.lga:
>
>> Adrienne, I'll look into the stored procedures as I do want
>> the
>> db to be as quick as possible. By chance, do you have any
>> resouces that may be helpful?
>>
>>
>
> Googling for it will give you some good hits, and I found this
> one to be
> pretty good:
> http://www.codeproject.com/database/hkstoredproc.asp
>
> One thing to try to stay away from is calling your stored
> procedures
> sp_somename because the server looks through all of its system
> procedures
> first, and that can slow the server down a little. If I were
> writing a
> stored procedure to get a list of images, I might name it
> GetPics.
>
> Also, be sure not to use SELECT *. Always explicitly list the
> columns
> you want to retrieve in your queries.
>
> --
> Adrienne Boswell at Home
> Arbpen Web Site Design Services
> http://www.cavalcade-of-coding.info
> Please respond to the group so others can share
>
Thanks again for the reply Adrienne, I'll definitely checkout the
codeproject.com resource.
I "DO" use the SELECT * in one call, but I use every column in
that. In a case like this, is it better to name all of the
columns?
Thanks again,
Chet
Navigation:
[Reply to this message]
|