Unanswered: Separate MSSQL Server from IIS Server?
For a production, business-critical application, should the data server (MSSQL) and the application server (IIS) always be on separate hardware?
I have a custom weekly timecard application that is used by a company of many thousands of employees worldwide. Most of the Web-based, large-scale applications deployed by this company are based on separate hardware for their data and applications servers, but my application is not being handled that way.
Is there a way (are there tools) to quantify the performance costs of having these two functions on a single piece of hardware versus two pieces of hardware?
Maverick Software Design
(847) 864-3600 x2