Simple, but very good work.

Keep writing!

~R

And good advice.

Very well written, good examples of common traps!

Every one must read this. Even if you write simple query, you should know these basic things. Otherwise you will end up with error prone queries.

Thanks a lot. Explained very well with proper examples.

Very very good wok keep posting these types of articles

Great article! I think most of these would be pretty quick to spot for the seasoned SQL developer, but nevertheless good to have them compiled in an article. You should write an article on set based computation using SQL with particular emphasis on how to replace cursors with set based processing under different scenarios :)

Very good stuff - keep on writing.

Shouldn't the title of this article be "Ten Common SQL Server Programming Mistakes".

I especially like the "Incorrect subquery column" section. I try to get the guys I work with here to use aliases more often. I find aliases help readability and maintenance, and more often than not help to catch simple mistakes like the one you highlighted. Even with these benefits they are still having none of it though and would rather just dump out column names.

I especially like the "Incorrect subquery column" section. I try to get the guys I work with here to use aliases more often. I find aliases help readability and maintenance, and more often than not help to catch simple mistakes like the one you highlighted. Even with these benefits they are still having none of it though and would rather just dump out column names.

Good article, I can't tell you how many times a few of these top 10's have made my queries go from 5 minutes to 5 seconds.

If I could add one more item to your list, I would add the times when you insert a lot of data into a table, you'll need to reindex that table before any subsequent queries. Other adds might include avoiding the CLR when possible. For those ASP.NET devs, use LINQ.

Bravo. I am going to send the link to my DBA's and Programmers. I have seen at least 2 of these mistakes in the last week of looking over scripts and stored procedures.

Wonderful work ! Keep it up !

Hi,

here's a great article that identifies all the 'broken' datatypes on your database.

http://www.sqlservercentral.com/articles/Admin/65138/