My immediate suggestion would be to install a secondary hard disk and have the SQL databases stored on that if you don't have that set up already. Lots of SQL queries will be heavy on disk I/O and hinder the overall performance of the machine if you are still using it for other tasks while SQL is running queries for you in the background.
A happy SQL server is one that has:
- Fast disk I/O access times
- Lots of memory to store the database in
- A fairly quick chip to process the queries to the disk, depending on the type of queries.
FWIW I believe SELECT and UPDATE are the most resource intensive out of the popular operations, which is why scalable services charge you more per query for these operations.
A definitive answer will depend on these factors as well as the questions Linker has mentioned.
A SQL profiling tool like ClearTrace can help you track down and optimize your queries as well:
