How to determine hardware option for a specified number of concurrent user in SQL Server?

  • I am new to DB Administration and I'd like to know how to determine exact hardware settings for  SQL Server Instance which gonna have 1000 concurrent users? What should be the CPU frequency or RAM. I know the min and max requirements, but it is obvious that this numbers are not the most efficient ones. If it has 1000 users does it mean it should have 1000 IOPS?
     Thanks in advance.

  • That answer is going to depend on more factors than just user count.

    For example, if your database is 100MB and those users are only pulling a single record a day, you won't need much.

    You have to get more details regarding database sizing and volume of activity expected. 

    I would ask the business the following types of questions:

    1. How much data? How much data in the long run? 
    2. Warehouse or OLTP?
    2. Who are the users? What types of queries will they be running?

    They aren't going to know or predict all the requirements, but it will get them thinking along these lines and hopefully get you more details.

    There isn't an exact science to this. Ultimately you are going to guestimate what is needed based on their requirements, and test/tweak in non production before going live.

  • elea.grig - Monday, August 20, 2018 12:30 PM

    I am new to DB Administration and I'd like to know how to determine exact hardware settings for  SQL Server Instance which gonna have 1000 concurrent users? What should be the CPU frequency or RAM. I know the min and max requirements, but it is obvious that this numbers are not the most efficient ones. If it has 1000 users does it mean it should have 1000 IOPS?
     Thanks in advance.

    As said in the previous post above, you need a whole lot more information before you can even take a stab at how big the power plug should be.  My recommendation is to hire a consultant to help you.  Just remember, with so little information, even a good consultant won't be able to help you.  You need to come up with much better info including the intended use and the 5-7 year plan for how big your data will grow, what the DR plan should be, etc, etc.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply