Need to design a net able to deal with 12000 users accessing SQL Server.
Hi there!
Could you indicate the best practices to size the servers and hosts?
TKS!
Hi there!
Could you indicate the best practices to size the servers and hosts?
TKS!
A book could be filled by this post. But let me just give you some practical advice. As you build your application, make sure to do load testing regularly. testing the app with load at the end of the project is asking for failure in a high load situation..
Evan
A lot of this depends on the database and the application(s) accessing it, the usage patterns, and rate of concurrent sessions. If you go with stored procedures (w/ low-complexity queries) that use a queuing system on well-indexed tables, hardware could be two large, clustered mirroring servers talking to a SAN. The system would be responsive and have little downtime.
If however your database is a mess and the applications are running amock with poorly written queries and people are lining up at the same time every day, you'll need 10x the hardware.
You also need to consider the importance of time sensitivity, write access, and geographic location of the users. If users are all over the world running select statements and data can be a few minutes old, replicate over the WAN into distributed read-only databases.
> Could you indicate the best practices to size the servers and hosts?
Yes.
Check out this post on database performance optimizations.
Then, get professional help. A top-tier consultant like Itzik or Kimberly would probably be more than you need, but do find somebody who does these sorts of things all the time. Don't expect to have someone walk you through everything you have to do online. There is too much complexity involved.