- Failure to Properly Configure AWE (Address Windowing Extensions) Memory Usage by not enabling SQL Server to use more than 2GB of RAM.
- Failure to Normalize
- Failure to Use Clustered Indexes
- Failure to Optimize by ignoring the impact of statistics, indexes etc
- Failure to Create SARGable Queries (SARG - Search ARGument)
- Wasted Network Bandwidth due to SQL Server's chatty behavior
- Improper Use of Cursors
- Failure to Use Full-Text Indexing where SARGable queries aren’t possible
- Failure to Use Multiple Data Files. Microsoft recommends a ratio of roughly 0.25 to 1 data file per file group per processor.
- Failure to Properly Size Data Types
10 Performance Secrets for SQL Server Developers
Michael K. Campbell highlights 10 common performance problems to avoid in the latest edition of SQL Server Magazine: