I am fully aware that both Exchange and SQL Server should never share the same box, as they both grab all the resources possible. But can you explain to me why none of these applications/systems should be on the same server?
To add insult to injury, no limitations were set on e-mail profiles and some are extreme.
End-users are generally unwilling to wait for RPC responses from Exchange, or wait for complex queries to complete against SQL Server. This means you should always plan on isolating these applications, or understanding through the use of Perfmon and WMI the end-user experience you are providing.
Do you have comments on this Ask the Expert Q&A? Let us know.
Related information from SearchExchange.com:
Dig Deeper on Exchange Server setup and troubleshooting
Related Q&A from Peter Tersteeg
Discover why using the Active Directory Migration Tool in a large Exchange Server environment may not be the best option for a successful migration. Continue Reading
Learn how to configure an Exchange 2003 server to act as a front-end server after a Microsoft Exchange/Windows upgrade and hardware migration. Continue Reading
Learn how to use the Recipient Update Service to configure multiple servers in the same organization to share the same recipient update policy. Continue Reading