Sage 100

Sage 100 Premium - docs recommend having SQL on the same box as Sage 100 server app. Is there a real reason for that? Customer already has a high end box running SQL server with not all that much use, but they want to keep it a SQL Server only machine.

Nope, we have clients with both configurations. I think it's better to keep them separated too.

Let's continue this discussion. What about Sage 100 and Sage CRM on the same box but virtualized. Performance issues? I have v4.5 advanced on a virtualized box and client keeps getting mysterious shutdowns. Frustrating as nothing is eliminating the issue. Will attempt an upgrade to v2015 in near future. What is odd is that there is nothing else running on the virtualized box. it was virtualized thinking that CRM would be installed but that hasn't happened. I have another client wanting to run Sage v2014 Adv AND CRM on the same box but virtualized servers.

My take on VM performance is you need to have separate physical drives for each VM. Processors keep getting faster, machines can have more RAM, but the storage I/O hasn't improved much (unless you use SSDs, and there is some debate on their long term reliability in heavy usage scenarios), so the drives are the bottleneck. CRM, especially if you are going to make it accessible from the internet, should be on a separate machine to minimize the damage if that machine gets hacked. @JeffSchwenk - mysterious shutdowns of MAS service or the VM itself?

We have a client Sage 100 premium installation with the applications hosted by a 3rd party. Application server (running Sage 100 & Sage CRM apps), SQL server (containing databases for CRM & SAGE 100, and two Terminal Servers (citrix) comprises the configuration. they are still going through testing before going live with the applications.