The join one is particularly bad as it can make your query run much slower as running multiple queries is almost never a win. A check for the opposite (multipl

The join one is particularly bad as it can make your query run much slower as running multiple queries is almost never a win. A check for the opposite (multiple queries when one is needed) would be better as then the query planner in the SQL engine can do a better job and you have fewer round trips. While the tool is a good idea, there need to be some proof that each of the patterns it's looking for are actually bad.