Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I need to calculate hardware for SQL Server. The application is business data-driven application with 500 requests per second. We plan to buy server with 4 intel Xeon CPU and 64 Gb RAM. Is it sufficiently?

share|improve this question

migrated from Oct 31 '11 at 6:14

This question came from our site for professional and enthusiast programmers.

closed as not a real question by Ward, Iain, Ben Pilbrow, Tom O'Connor, Mark Henderson Oct 31 '11 at 8:34

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

What storage? Are the requests reads or writes? How big will the database be? How fast will the database grow? And how to do plan to provide High Availability/Disaster Recovery? If you don't have any plan for HA, how are you going to do maintenance and patching? – Remus Rusanu Oct 31 '11 at 5:49
What is the most limiting factor of a database? And what do you nto talk about at all? DISC IO. The question is totally unanswerable in this form. Point. The server is either powerfull or total crap depending on the discs. Get a server that can stock 30+ discs - SuperMicro sells them (2 rack units = space for 72 discs + the server hardware - mobo etc.). – TomTom Oct 31 '11 at 7:21

The specifications you've come up with looks like a decent start for "some kind of database" that you don't know much about. But you can get a very nasty surprise, finding out that this doesn't work at all.

It's impossible to tell with the amount of information given.

A query is not a fixed cost. If it was 500 light queries per second - you could scale down significantly. If they are really complex queries, you might need a lot more than you've specified. If it's a poorly written application, it might need a rewrite to be able to run decently fast.

To best be able to answer this, you need to establish a good baseline for the application; How much resources does it consume under realistic load? The developers of the application should have some knowledge about this as well.

You should also keep storage in mind - which needs to satisfy the throughput required, and have at least a basic level of redundancy to avoid data loss.

I'm assuming you've got backup and high availability-concerns covered.

share|improve this answer