I share the same philosophy as Jerry. Once you have a SQL server in place, there is a good chance that it will be used for other applications at some point. Depending on these applications, the number of I/O operations might significantly change and impact Sage's performance.
If the user base for Sage is larger, then I put SQL on a dedicated SQL server. If there are only a few users who use Sage simultaneously, then utilizing the same server for both Sage and SQL will do.
Most environments today are based on virtualization (e.g., MS HyperV). In those environments, there is no physical network cable between the two virtual servers. I am not a virtualization expert, but I believe that with properly configured virtual NICs, the difference between a (virtual) two server setup and a one server setup shouldn't be too big. Especially if we consider that Sage and SQL on the same server might have to compete for resources. Is there a virtualization pro here that can shed some light?
I also always wonder if using the IP address vs. the UNC path gives any performance advantage.
------------------------------
Bastian Boesner-Worth
Regional Consulting Manager
SWK Technologies Inc.
973-396-1721
------------------------------