Re: Select *
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Mon, 5 Dec 2005 22:34:15 +0000 (UTC)
Trevor Best (nospam@xxxxxxxxxxxxxxxxx) writes:
> If you have "select * from table1" in code and drop column2 how is that
> different from having "select column1, column2, column3 from table1" in
> code and dropping column2? (apart from the error ocurring on a different
> line of code of course:-))
The difference is that
1) "SELECT column1, column2..." will bomb. A SELECT * could continue to
work, but yeild incorrect results.
2) If you are using stored procedures, you can use sysdepends to track
whether the column is used, and you would know that it is used. With
SELECT * you don't have an idea.
3) Even if you don't use stored procedure, you can still search the code
for references to the column.
--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.
- References:
- Select *
- From: Ray Allison
- Re: Select *
- From: Danny
- Re: Select *
- From: Trevor Best
- Select *
- Prev by Date: Re: MSE
- Next by Date: Re: help with grouping query...
- Previous by thread: Re: Select *
- Next by thread: Re: Select *
- Index(es):
Relevant Pages
|
