Posted by Leythos on 09/17/07 21:06

In article <Uv-dnaiBfeHjf3PbRVnyugA@giganews.com>, no@email says...
> I know that in order to reduce network traffic you should always select only
> the columns you require but I have a stored procedure which must **always**
> return all columns from a specific table.
>
> When returning all columns from a table is there any performance gain (or
> any other reason) for using SELECT col1, col2 etc... instead of just SELECT
> * ?
>
> I can immediately think of a disadvantage which is that if you include named
> columns in your SELECT then you must update the stored procedure each time a
> column is added to the table, using SELECT * gets around this so the stored
> procedure will never need to be modified.
>
> Would anyone care to share their thoughts on the above?

Imagine if you returned columns that the application requesting the info
didn't know how to handle. Select * means you didn't know what you were
expecting on one side or the other or both....

--

Leythos
- Igitur qui desiderat pacem, praeparet bellum.
- Calling an illegal alien an "undocumented worker" is like calling a
drug dealer an "unlicensed pharmacist"
spam999free@rrohio.com (remove 999 for proper email address)

• Next in forum: Re: SELECT * vs SELECT col1, col2
• Prev in forum: SELECT * vs SELECT col1, col2
• Thread view: Re: SELECT * vs SELECT col1, col2

[Reply to this message]