Well how 'wide' are the tables
What is the selectivity of your indexes
How much memory/CPU's will you have
Our current Production machine has 170 million rows in tables that are horizontaly partitioned with 4 HT CPU's and 4 GB of RAM
This is not a read only DB by the way
I rarely go above 50% CPU utilization
You have to do some testing
There are systems out there with billions of rows
Also think about putting the most accessed tables on seperate filegroups/drives
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.