Create simple Stored Procedures?

[shumaker]

IF I have a very simple query, something like
SELECT COLUMNNAME FROM TABLE
and I know I will use it at least in a few different places, then would
it be good design to create a stored procedure for the query?

It would seem if I did, then I will quickly accumulate a large number
of stored procedures, and I'm not sure if this is bad?

Thanks.

[Tom van Stiphout]

On 28 Apr 2005 07:36:49 -0700, sh******@cs.fsu.edu wrote:

I would not create a new sproc for each combination of fields I might
need for my app.

For queries that are mostly based on a single table, I typically
create 2 sprocs: one that returns 2 columns: the primary key and the
main description field. This sproc I would use in dropdown lists.
The second query selects all fields. I use this one even if I only
need a couple of fields.

There are of course sensible exceptions to these rules.

-Tom.

IF I have a very simple query, something like
SELECT COLUMNNAME FROM TABLE
and I know I will use it at least in a few different places, then would
it be good design to create a stored procedure for the query?

It would seem if I did, then I will quickly accumulate a large number
of stored procedures, and I'm not sure if this is bad?

Thanks.