Solved

Sharepoint setup question

Posted on 2014-11-21
3
159 Views
Last Modified: 2014-11-24
I have a VM, 2012 R2 with sharepoint 2013 on it.  I did a single server install where SP and SQL are on the same server. The VM has tons of resources!

It's slow!

I was told that sharepoint and SWL on the same box is bad and that my speed issue is related to the single server install.

I'm looking for thoughts on that.  Can I do a single server install for production or should I split them up?

What's a best practice for a production Sharepoint server?

Thanks

Cliff
0
Comment
Question by:crp0499
  • 2
3 Comments
 
LVL 7

Accepted Solution

by:
Ray earned 500 total points
ID: 40458297
It's all depends on many factors (number of users, number of SP sites etc).  We have clients started with a single box and add more servers to the farm or move to a standalone SQL box at a later time when needed.  

With SQL and SP on the same box, make sure you limit the max memory on the SQL server.  As far as CPU, check the resource monitor and added more as needed.   With 10 users and 10 sites; 16 CPU and 32GB RAM seems to be a good start.

Here're some guideline and best practices for virtualizing and managing SharePoint 2013
http://download.microsoft.com/download/0/0/1/001ADCCC-A45B-47E3-8DA4-ED51E3208021/Best_Practices_for_Virtualizing_and_Managing_SharePoint_2013.pdf
0
 

Author Comment

by:crp0499
ID: 40458395
We have one VM, 4 CPUs and 16 gigs RAM on fast storage.  We will support one site and 20 users.  Very small implementation.

BUT, the site is slow and sluggish.  I was told it was because the SP and SQL were on the same box.

From what you are telling me, it seems fine for our use.
0
 
LVL 7

Expert Comment

by:Ray
ID: 40458478
Both SP and SQL are resource demanding applications.  If you have Web App enabled (Allow user to edit Word/Excel via browser), you will need more resources.  You should increase the CPU to 16 and RAM to 32 GB; monitor the server performance and adjust accordingly.

Remember to limit the MAX RAM for SQL and setup SQL tuning (Index/Stats update). For SP Search/Crawler, schedule the full crawl after hours and incremental every few hours (depends on your requirement).  Only turn on the required SP services and farm features.

In a ideal world, running it on a web farm and SQL cluster will provide  high availability and scalability.   With the scalability of the SP farm, it will be possible when needed.
0

Featured Post

Live: Real-Time Solutions, Start Here

Receive instant 1:1 support from technology experts, using our real-time conversation and whiteboard interface. Your first 5 minutes are always free.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Microsoft SharePoint Foundation 2010 and Microsoft SharePoint Server 2010 do not offer the option to configure the location of the SharePoint diagnostic trace log files during installation.  This can, however, be configured through Central Administr…
These days socially coordinated efforts have turned into a critical requirement for enterprises.
In a recent question (https://www.experts-exchange.com/questions/28997919/Pagination-in-Adobe-Acrobat.html) here at Experts Exchange, a member asked how to add page numbers to a PDF file using Adobe Acrobat XI Pro. This short video Micro Tutorial sh…
The Email Laundry PDF encryption service allows companies to send confidential encrypted  emails to anybody. The PDF document can also contain attachments that are embedded in the encrypted PDF. The password is randomly generated by The Email Laundr…

776 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question