Results 1 to 2 of 2

Thread: Server Sizing

  1. #1
    Join Date
    Jul 2010

    Unanswered: Server Sizing


    First post and what I think is a tricky question...

    We have a project to create a number of databases in SQL server.

    One of them will be quite big. We are expecting 10-20 smallish transactions a second and one table in particular (for legal reasons) will be > 100 million records within 12 months.

    How can I estimate the hardware requirements for this? Any thoughts?

    Their will be a pair of mirror'ed SQL servers for high availability. Is it best to use 64 bit? 32-bit would be more convenient.

    How much memory would you recommend? CPUs?

    Like I said, tricky question. All advice welcome.

    Thanks in advance.

  2. #2
    Join Date
    Jul 2003
    San Antonio, TX
    Usually it ends up being a big question, with a long answer, but mostly with front-loaded number of questions back to you, such as:

    - Number of databases, users, nature of usage (transactional, reporting, ETL, etc.);
    - Availability requirements or SLA's for each database, including recovery requirements;
    - Database structure for each database, and its estimated projected growth, etc.

    And what do you mean when you say "a pair of mirror'd SQL Servers for high availability"? Are you going to implement database mirroring, or you're talking (not very clearly) about a 2-node cluster?
    "The data in a record depends on the Key to the record, the Whole Key, and
    nothing but the Key, so help me Codd."

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts