Posted by Knowledgy on 01/19/08 12:08

Adding columns to tables frequently points to a poor database design.

--
Sincerely,
John K
Knowledgy Consulting
http://knowledgy.org

Atlanta's Business Intelligence and Data Warehouse Experts


"Danny Burton" <no@email> wrote in message
news:Uv-dnaiBfeHjf3PbRVnyugA@giganews.com...
>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?
>
> Thanks,
>
> Clive
>
>
>
>
>

• Next in forum: I need to know where mssql server stores its data.
• Prev in forum: Re: New Release of Mogwai ERDesigner NG
• Thread view: Re: SELECT * vs SELECT col1, col2

[Reply to this message]