Home > Ask the SQL Server Experts > Archive: SQL Server 2005 Questions & Answers > Determining number of servers needed for large member site
Ask The SQL Server Expert: Questions & Answers
EMAIL THIS

Determining number of servers needed for large member site

Adam Machanic EXPERT RESPONSE FROM: Adam Machanic

Pose a Question
Other SQL Server Categories
Meet all SQL Server Experts
Become an Expert for this site


Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us   


>
QUESTION POSED ON: 25 July 2006
I would like to know the number of servers needed for a large member site? I am aware that a number of problems can arise when a site has a huge number of members, but an insufficient number of servers where users simultaneously search through the MySQL database for other members' profiles. Problems include down time, slow server performance, slow script and even outages to users.
Do you have an idea how many servers are needed to handle 100,000 concurrent users of a member site?


Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us   


RELATED CONTENT
SQL Server High Availability, Scalability and Reliability
Top load balancing methods for SQL Server
Maintaining high availability of SQL Server virtual machines
Creating fault-tolerant SQL Server installations
Scaling up vs. scaling out with SQL Server 2008
How to configure storage in SQL Server database with more writes than reads
SQL Server database replication tutorial
Licensing a standby server for SQL Server replication
Get SQL Server log shipping functionality without Enterprise Edition
Monitor database mirroring and replication after a SQL Server upgrade
Upgrade live applications to SQL Server 2005 for high availability
SQL Server High Availability, Scalability and Reliability Research

Microsoft SQL Server Performance Monitoring and Tuning
Performance implications of transaction log autogrowth in SQL Server
The short course on how SQL Server really works
Determining the source of full transaction logs in SQL Server
Improving SQL Server full-text search performance
New GROUP BY option provides better data control in SQL Server 2008
Microsoft SQL Server 2008 Resource Governor primer
Examining data files when SQL Server tempdb is full
Testing transaction log autogrowth behavior in SQL Server
Meeting business needs with SQL Server full-text search
Using dynamic management views to improve SQL Server index effectiveness

Archive: SQL Server 2005
Stored procedure concurrency problems in SQL Server 2005
SQL vs. T-SQL
Database Snapshots: Creating read-only copies of a database
Upgrading SQL Servers
SQL Server 2005 Enterprise Edition vs. Standard Edition
Encryption failures when upgrading to SQL Server 2005
Upgrading to SQL Server 2005 while maintaining .adp access
Modifying a query to show navigation path
Viewing SQL Server 2005 data via Windows Forms
SQL Server 2005 upgrade issues

RELATED GLOSSARY TERMS
Terms from Whatis.com − the technology online dictionary
contiguity  (SearchSQLServer.com)
contiguous  (SearchSQLServer.com)
drilldown  (SearchSQLServer.com)
hashing  (SearchSQLServer.com)
hybrid online analytical processing  (SearchSQLServer.com)

RELATED RESOURCES
2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems
Search Bitpipe.com for the latest white papers and business webcasts
Whatis.com, the online computer dictionary


It is impossible to predict how many servers your site will need without understanding the nature of the applications running on the servers, the users using the applications, and the servers' specifications. In addition, there are questions of what high-availability tactics you'll want to employ, if any.
Some factors you should look at include:

  • How are the applications architected from a scalability point of view? Is there a middle tier that does data caching in order to take load off of the database servers? Can the data be partitioned in order to support a scale-out strategy, or must scale-up be employed if you need to support more concurrent load? Are the applications' interfaces into the data chatty (i.e. do they make a lot of requests for data)?

  • How often do users log in? What do users do while they're on the site, and how much traffic will they generate? How many simultaneous users will the application have to support in peak load times?

    Once you've considered these factors, take the data you've collected and create stress tests to validate the load requirements. Only by testing can you determine how much load the application can handle, and whether you'll be able to scale it by adding more servers.




  • Search and Browse the Expert Answer Center
    Search and browse more than 25,000 question and answer pairs from more than 250 TechTarget industry experts.
    Browse our Expert Advice



    SQL Solutions - SQL Database Design
    HomeNewsTopicsITKnowledge ExchangeTipsAsk the ExpertsMultimediaWhite PapersIT Downloads
    About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
    SEARCH 
    TechTarget provides technology professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective purchase decisions and managing their organizations' technology projects - with its network of technology-specific websites, events and online magazines.

    TechTarget Corporate Web Site  |  Media Kits  |  Site Map




    All Rights Reserved, Copyright 2005 - 2009, TechTarget | Read our Privacy Policy
      TechTarget - The IT Media ROI Experts