Link to home
Start Free TrialLog in
Avatar of crp0499
crp0499Flag for United States of America

asked on

Sharepoint setup question

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
ASKER CERTIFIED SOLUTION
Avatar of Ray
Ray
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of crp0499

ASKER

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.
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.