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 Deployment and Migration Advice
Related Q&A from Peter Tersteeg
If recently created mailboxes are not displayed in the GAL after a migration to Exchange 2007, Active Directory (AD) has yet to replicate the ... Continue Reading
If you are migrating mailboxes across domains after an upgrade to Exchange Server 2007, you will need to update the Exchange Management Console. Continue Reading
Items deleted before an Exchange Server migration will not carry over to the new server, even if a Deleted Items Retention period is set. Find out ... Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.