• 1 min read

SELECT * AND SQL Azure

[This article was contributed by the SQL Azure team.]Every good DBA and developer knows that you should not use: SELECT * FROM [Table] in your queries to a database, especially if you are not…

[This article was contributed by the SQL Azure team.]

Every good DBA and developer knows that you should not use:

SELECT * FROM [Table]

in your queries to a database, especially if you are not using all the columns returned. Just return the columns you need in the SELECT statement. Using SELECT * can cause extra paging, RFID lookups, unneeded table locking and hinders any future attempts to create a covered index. In summary, it is bad for performance.

However, with SQL Azure there is an additional reason not to use SELECT *, you have to pay for the data transferred. If you are outside the data center (not a Windows Azure application) then you end up paying for the data transferred from your query. If you request columns that you are not using, you will be paying for data to be transferred that you will never use.

So if removing the SELECT * queries have been on your TO-DO list, now is a good time to clean them up before you move to SQL Azure.