And if you do, how much memory do you have on the server?
I would think they should be on separate servers.
We have a many clients running SQL and Sage server on the same machine. Memory varies, depending on usage, but a memory cap on SQL is a good idea (at about 50% of the server's memory, to ensure there is enough for Windows, Sage...).
The main guidance I give for the same server vs. separate server is whether SQL server is used for other things. Occasionally the Sage server needs to reboot (for various reasons), and it would not be good to take down the SQL service at the same time, if it is being used by other systems.
We have a many clients running SQL and Sage server on the same machine. Memory varies, depending on usage, but a memory cap on SQL is a good idea (at about 50% of the server's memory, to ensure there is enough for Windows, Sage...).
The main guidance I give for the same server vs. separate server is whether SQL server is used for other things. Occasionally the Sage server needs to reboot (for various reasons), and it would not be good to take down the SQL service at the same time, if it is being used by other systems.
*Community Hub is the new name for Sage City