SQL and Exchange togerther

Posted on 2008-11-03
Last Modified: 2012-05-05
I am trying to configure my network on limited budget - like everyone.

My question is - are their any problems with running an exchange server and sql server on same system.
The machine has ample power to do this - it is a monster.

Is this ok / not ok / advised / not advised / stupid / a complete no no

Please provide an answer, and why/for what reason.

If i was to do this i would bind exchange to one NIC and run all other traffic through another
Question by:dexterhome
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
LVL 15

Accepted Solution

Greg Besso earned 250 total points
ID: 22868548
I'm sure it is not recommended, but also possible.

If anything, you can throttle SQL to only use a certain amount of memory.
Also, if it is truly a monster, can you create separate RAID partitions for SQL data, and for Exchange data?

Also by monster, let's clarify. How much memory, how many cores/processors, how many hard disks at which speed, and how many raid configurations will it support?

Perhaps you can run Virtual Server 2005 R2 on this and setup virtual servers instead?
How many users are you supporting?

LVL 12

Assisted Solution

weareit earned 250 total points
ID: 22868549
The short answer is yes.

The long answer is, It is feasible to do, but you must understand the performance strains that you will be placing on the server.  I have a lot of small businesses that I support and a question like this is really a matter of budget.

For the best results you would want to run Exchange and SQL on separate servers as they are both memory hogs.  In their defense though, both Exchange and SQL do a wonderful job of releasing memory they are using back to the operating system when the operating system needs it.  Another reason to segregate them is the "eggs in one basket" belief.  Can you go without both of these servers at the same time in case of a critical outage?

Here are the recommendations I make:

First ensure you have ample processing power.
Second, ensure (this is a must) you have a dual back plane configuration (segregate the OS drives from the DATA drives onto two separate RAID backplanes/controllers).  The OS can be configured as a mirrored set and the DATA should be configured at least as a RAID5.  With that in mind, have the databases or even both the databases and the primary applications (in this case SQL and Exchange) installed to and stored on the RAID5 disk set.
Third, ensure you have amble memory (4 - 8gb is generally the accepted standard) but understand that your OS may not recognize/address anything above 4GB.

For the question about network traffic.  It would ease the bottleneck at the port level, but using a network load balancing pair would probably give you a better overall performance and redundancy factor.  It depends on the number of users you have and how many connections to the server you will be servicing.


Author Closing Comment

ID: 31512754
Thanks for your answers. I thought about it after i posted the question. this would work because, how would SBS server run SQL.
Machine is 2xquad core xeon 3gh / 8gb ram / server 2003-64 bit, so no issues with that. Thanks again.
LVL 12

Expert Comment

ID: 23104454
To just jump in with a small tidbit of information.

The standard version of SBS 2003 uses MSDE which is based on SQL 2000 Server Technology.  The Premium version of SBS 2003 uses SQL 2005 Workgroup Edition and according to Microsoft, while you can install SQL 2005 Standard or SQL 2005 Enterprise onto a SBS 2003 Server, it is not supported.

While I have not personally tried to install SQL 2005 Standard or SQL 2005 Enterprise onto a Standard SBS 2003 Server, I have installed SQL 2005 Express Edition and migrated all MSDE instances on many Standard SBS 2003 Servers with little to no problems.

It should also be noted that SBS 2008 Standard uses the Windows Internal Database Technology set which is based on SQL 2005.  SBS 2008 Premium includes SQL 2008 Standard for Small Business and if needed (because of incompatibility between your line of business application(s) database and the SQL version) a copy of SQL 2005 Standard.


Featured Post

Does Powershell have you tied up in knots?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Creating a View from a CTE 15 39
What is needed to become a DBA? 7 46
HIghlights of SSIS? 3 40
How to create and use encrypted columns in SQL 2005? 15 53
Lotus Notes – formerly IBM Notes – is an email client application, while IBM Domino (earlier Lotus Domino) is an email server. The client possesses a set of features that are even more advanced as compared to that of Outlook. Likewise, IBM Domino is…
This article lists the top 5 free OST to PST Converter Tools. These tools save a lot of time for users when they want to convert OST to PST after their exchange server is no longer available or some other critical issue with exchange server or impor…
This video discusses moving either the default database or any database to a new volume.
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync. To learn more about CodeTwo Exchange Sync and download the free trial, go to:…

738 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question