SQL and Exchange both fall under the category of "does not play well with others" in my opinion. Unless both databases are very small with very few concurrent transactions, or the server is part of a really beefy cluster, I'd highly recommend against it. It's just not worth the headache. Both of them are notorious hogs of system resources; both kind of expand to use whatever's available.
I'd also advise against it based on "single point of failure" doctrine - your life would probably not be fun if both your SQL server and Exchange server were dead at the same time. On SBS, with small d/b's and a limited number of users, chances are good you'd be fine - SBS is designed to share system resources that way. That's why the number of possible users is so limited. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange To subscribe: http://e-newsletters.internet.com/discussionlists.html/ To unsubscribe send a blank email to [EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with.
