At first I didn't want to post a story on the site about this since it falls outside the realm of what we usually try to present here, but since a number of IT professionals are not specifically database programmers or designers yet still need to have a good idea of what could affect their organization's database performance, I thought I'd share an article that came out yesterday written by Sean McCown at InfoWorld. The article outlines many of the most common (and often lazy) things SQL database developers do that could affect performance.
7 performance tips for faster SQL queries
It's easy to create database code that slows down query results or ties up the database unnecessarily -- unless you follow these tips
A lot of the tips are very similar in nature, basically saying that you want to reduce your query size as much as possible in addition to the number of times you query tables (especially large ones), but it's not just a "well, duh" type of article. It's well written and is clear on the issues, though it assumes you have at least a basic understanding of SQL databases. If you are looking to speed up your SQL queries or just want to update your mental memory banks on database optimization, take a look at Sean's article and give it a quick read-through.