Windows 2000 Server Topic

alent1234

Diamond Member
Dec 15, 2002
3,915
0
0
some features won't work and the last thing you want to do is install exchange and SQL on the same box
 

AstroGuardian

Senior member
May 8, 2006
842
0
0
Originally posted by: alent1234
some features won't work and the last thing you want to do is install exchange and SQL on the same box

How do you mean features will not work? I never done it before that's why i am asking.
You think that Exchange and MSSQL will not do good on a same machine? Is that what you are saying? Because if it is so, i will install them on separate machines but a second server should be employed.

Can you please elaborate that a little bit more?

Thanks
 

stash

Diamond Member
Jun 22, 2000
5,468
0
0
RPC/HTTPS won't work if Exchange 2003 is installed on Windows 2000, I think.

SQL and Exchange on the same server is a terrible idea. They are both databases, and therefore have high amounts of I/O. In addition, Exchange is programmed to use as much memory as it can, which would cause problems with SQL.
 

networkman

Lifer
Apr 23, 2000
10,436
1
0
Another vote for keeping SQL and Exchange on seperate servers. That's what we do at my workplace. Even more important when your VoIP system has tie-ins to the Exchange server and vice-versa. I can only imagine the nightmare we'd have if that were also trying to run with SQL on the same box! :shocked:
 

RebateMonger

Elite Member
Dec 24, 2005
11,586
0
0
It certainly depends on what kind of usage we're talking about. Many SBS 2003 Servers have SQL 2000 installed, along with their built-in Exhange Server. As well as multiple instances of MSDE (SQL "Light").

If you have 1000 Exchange mailboxes and 1000 SQL users online, then you'd certainly want separate servers. If you have 50 users and SQL contains your accounting or CRM database, then a single server should be fine.
 

alent1234

Diamond Member
Dec 15, 2002
3,915
0
0
Originally posted by: stash
RPC/HTTPS won't work if Exchange 2003 is installed on Windows 2000, I think.

SQL and Exchange on the same server is a terrible idea. They are both databases, and therefore have high amounts of I/O. In addition, Exchange is programmed to use as much memory as it can, which would cause problems with SQL.

what he said

and exchange is basically MS Access on steroids and MS says anything more than 4GB of RAM may not be a good idea. This is supposed to be fixed in Exchange 2007. SQL loves RAM. the more the better.

there is also the issue of what to do if one goes bonkers. SQL is easy to fix. detach and reattach db on another server in the worst case. Exchange is a nightmare if things get bad.