Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
?
Solved

Sharepoint setup question

Posted on 2014-11-21
3
Medium Priority
?
182 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 2000 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

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

Question has a verified solution.

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

I thought I'd write this up for anyone who has a request to create an anonymous whistle-blower-type submission form created using SharePoint 2010 (this would probably work the same for 2013). It's not 100% fool-proof but it's as close as you can get…
A while back, I ran into a situation where I was trying to use the calculated columns feature in SharePoint 2013 to do some simple math using values in two lists. Between certain data types not being accessible, and also with trying to make a one to…
Loops Section Overview
With just a little bit of  SQL and VBA, many doors open to cool things like synchronize a list box to display data relevant to other information on a form.  If you have never written code or looked at an SQL statement before, no problem! ...  give i…
Suggested Courses
Course of the Month13 days, 1 hour left to enroll

579 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