Originally Posted by adamli9
That's good info. Our BES will always be on its own physical server, but SQL might be shared if it's on another physical server. It'll ultimately be up to the windows server group, but I'll tell them what you said. Thanks.
OK... while you're passing along suggestion to them - a couple of other considerations that are significant:
Depending on the database and the applications hitting it, SQL Server performance can improve dramatically given more RAM. In general, it makes excellent use of RAM, and can cache indexes in RAM when there's enough space, making lookups (as in queries, joins, etc) dramatically faster.
Other consideration is I/O: SQL performance is heavily dependent on disk I/O, and this is an area that is often ignored. Fast I/O makes a huge difference, and the drive controller configuration is important as well. Multi-threading controllers, large amounts of cache memory on the controller, and minimum contention on the drive/controller all help SQL performance.
Good idea, before all is locked in stone, to get some input from an MS SQL tuning guru re: hardware / network configuration for your server. I've been in IT/technology a LONG time, and been amazed at some of performance hits resulting simply from a lack of proper information at the right point in the decision making process.
Good luck with all of this...