Sage 100

Question: How to determine the equivalent virtual processor to a physical processor. Sage recommends a Intel or AMD 64-bit capable, such as Intel Xeon or Quad-Core AMD Opteron processor for the application server... but how does that translate to a virtual server? Seems the language is ""cores"", not CPUs. My guess is that a quad-core physical processor would be like ""4 cores"" - am I even remotely close? Why I am asking: Recently moved a client from Sage 100 ADV to PREM. Having performance issues - very slow postings. IT says that SQL server is not showing signs of stress (since I am uncertain how to measure that on my own - I am not entirely convinced).. However the application server CPU is at 90 to 100% during the posting process. Application server is virtual. This is a 15 users system where most users are doing some sort of data entry to AP, AR or PO. Postings that used to take a could minutes now take 20 minutes. They have a ""virtual"" processor of a single 2.4 Ghz. Seems to me that they need to allocate more processing power to this VM Client is asking me about the equivalents... Thanks in advance to the uber techy person who knows the answer to this!

I don't know the technical difference however, I think you're on the right track (cores). I am pretty sure there was a Sage 100 Premium discussion maybe within the last year where a customer upgraded to Premium and the speed was oddly slow until the increased or perhaps doubled the cores alloted to the virtual machine.

What version of Sage 100 Premium? What is the server OS? How much memory does the server have? How much memory is allocated to SQL Server? What version of SQL Server is it? Is the server a domain controller? Is the server running any other program besides SQL and Sage 100, (like Exchange)? Are there shared printers on the server? What brand of antivirus is on the server? Are the recommended exclusions and configurations set up? Is SQL on the same VM as Sage 100? If so, are they on separate volumes?

If SQL and Sage 100 are on the same server, make sure that SQL RAM usage is restricted to no more than 75%. If using a VM, make sure it is assigned multiple cores

@DougHiggs OK here goes... v2015 Prem OS - Windows 2012 R2 (VMware 5.5) 4 GB of RAM - monitoring shows RAM not being taxed SQL 2008 R2 SP3 - virtual - 2 CPUS. 8 GB memory (WMware 5.5) SQL is dedicated to SQL Application server has ONLY Sage 100 No shared printers Antivirus brand - Good question - I will confirm ( I do not think it is Trend Micro) Recommended exclusions are set. SQL and Sage are on different VM Hosts ( I think, and will confirm)

@PhilMcIntosh - Good points. SQL and Sage on different boxes

If SQL is on a VM by itself, and memory is not being taxed, the SQL's RAM is likely being too restricted. The more of the database you can keep in memory, the faster it will run. I also recall that, at least at one point Sage was recommending they be on the same box. I have no idea if there was an actual reason for that recommendation. IT should check on the network throughput between the two VMs.

4GB of RAM for 15 users is not nearly enough. RAM is inexpensive. I would up it to 32GB or 64GB minimum. If SQL and Sage 100 are in separate physical machines there could be a bottleneck transmitting data between the servers.

The application server should have at least 2 vCPU and more RAM would be nice although I'm not sure it's really the bottleneck. You could have IT run an iperf to make sure the bandwidth between the two servers is gigabit-class. http://xenserver.org/discuss-virtualization/virtualization-blog/entry/basic-network-testing-with-iperf.html

Thank you all for your input and validation! This gives me a good foundation to speak to the client regarding server configs. Very much appreciated!. I will be sure to circle back and update on the end result.

Doug is right. I have 4 gigs of ram on my phone! SQL is a memory hog. It should have 24 to 32 gigs of ram and make sure you set it to not use more than 75% of the machines total RAM or it will often start grabbing disk based paging memory and that will be all she wrote in terms of performance.