Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>My experience suggests that (within limits) the hardware is typically the least important factor in database performance.</p> <p>Assuming that you have enough memory to keep commonly used data in cache, then your CPU speed may vary 10-50% between a top-of the line machine and a common or garden box.</p> <p>However, a missing index in an important search, or a poorly written recursive trigger could easily make a difference of 1,000% or 10,000% or more in your response times.</p> <p>Without knowing exactly your table structure and row counts, I think anybody would suggest that your your hardware looks amply sufficient. It is only your database structure which will kill you. :)</p> <p>UPDATE:</p> <p>Without knowing the specific queries and your index details, there's not much more we can do. And in general, even knowing the queries, it's often very difficult to optimize without actually installing and running the queries with realistic data sets.</p> <p>Given the cost of the server, and the cost of your time, I think you need to invest thirty bucks in a book. Then install your database with test data, run the queries, and see what runs well and what runs badly. Fix, rinse, and repeat.</p> <p>Both of these books are specific to SQL Server and both have high ratings:</p> <p><a href="http://rads.stackoverflow.com/amzn/click/0735621969" rel="nofollow noreferrer">http://www.amazon.com/Inside-Microsoft%C2%AE-SQL-Server-2005/dp/0735621969/ref=sr_1_1</a></p> <p><a href="http://rads.stackoverflow.com/amzn/click/B001GAQ53E" rel="nofollow noreferrer">http://www.amazon.com/Server-Performance-Tuning-Distilled-Second/dp/B001GAQ53E/ref=sr_1_5</a></p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload