We help IT Professionals succeed at work.

Size a Sharepoint Server for 3000 users

1,933 Views
Last Modified: 2013-11-14
Hello,

My boss has asked to size up a Sharepoint back en SQL 2005 server for monday (never had to size up anything related to Sharepoint).  Knowing that Sharepoint application does use resource consuming functionnalities such as Full Text searches and BLOB's, I was wandering about what kind of architecture are we looking into.  Also what kind of disk volume are we looking for?  Did anyobdy had any experience into sizing a similar architecture....There will be about 3000 users using that system....Thank you for your feedback.
Comment
Watch Question

Top Expert 2007

Commented:
I've never sized a server for 3K sharepoint users, but if I look at our server and number of users, this is what it would take. Are that 3000 concurrent users ... ?

... LARGE !!!!
Go for at least 16GB of memory, 4 dual core processors and 1 TB of diskspace ... or you'll find yourself upgrading the hardware within the year. Ofcourse the disk size depends on what you will put into sharepoint, but my experience is that it will consume mojar GBs. So if I were in your shoes, I would try to go for the TB.

... and you probably need a DR machine as well with 3000 users, it's hardly to be non-critical :-)

Hope this helps ...
Racim BOUDJAKDJIDatabase Architect - Dba - Data Scientist
CERTIFIED EXPERT

Author

Commented:
<<Are that 3000 concurrent users ... ?>>
No.  That's the total number of users.  I expect about 40% of these users to consult the server each day.  I expect about 50% of the activity to be focused on searches, 40% on regular SQL queries and 10% on overhead (monitoring, admnistration) needs.  As for sizing,  I want to go for a 2Tb configuration that may evolve in time to a bigger configuration....
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION
Racim BOUDJAKDJIDatabase Architect - Dba - Data Scientist
CERTIFIED EXPERT

Author

Commented:
Thanks for the information...On the following scenario :

Web and search servers       2 GB       200 GB       2       Dual 2.8 GHz Pentium 4
Database server       2 GB       200 GB       1       Dual 2.8 GHz Pentium 4
Index management server       2 GB       100 GB       1       Dual 2.8 GHz Pentium 4

What is exactly the Index management server?  Is it a physical location for the full text catalog?  Is the IO load more important on that server?  Can I really use only one SQL Server with a quad core and fast disks....
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION
Top Expert 2007
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION

Gain unlimited access to on-demand training courses with an Experts Exchange subscription.

Get Access
Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Empower Your Career
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE

Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

  • Troubleshooting
  • Research
  • Professional Opinions
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.