Qure addresses SQL programming mistakes

Qure addresses half of most common SQL programming mistakes

Posted by Ami Levin on 10 September 2009 | 0 Comments

I recently ran across a very interesting article describing the "ten common SQL programming mistakes". The article, which was written by SQL Server MVP Plamen Ratchev and published on Simple-Talk, presents, based on the writer's extensive experience, some of the more common mistakes made by professional while coding SQL. Obviously, such a list is not exhaustive, but I believe that many of my colleagues would agree to a large part of it.

After I went over the entire list I realized that DBSophic's solution, Qure, actually addresses half of those mistakes. The meaning is that by adopting Qure, organizations can save much time and resources and substantially reduce the number of these mistakes, allowing their DBA's to pay more attention to other urgent issues.  

It is interesting to note that, while Qure addresses half of the problems, the second half are logical query errors which may either raise errors or return unexpected results.

In order to validate my point I have divided Ratchev's common mistakes into three groups:

Issues fully addressed by Qure

• NULLs and the NOT IN predicate
• Functions on indexed columns in predicates
• Data type mismatch in predicates
• Use of SELECT
• Scalar user-defined functions

Issues that Qure addresses partially or indirectly

• Overuse of cursors

Logical Query Issues

• Incorrect sub query column
• Predicate evaluation order
• Outer joins and placement of predicates
• Sub queries that return more than one value