×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




Walden H. Leverich skrev den 08-08-2008 18:46:
Walden is saying (I think) the Windows model is to have one application/database per server

Perhaps not that far, but that's the general idea. I have no problem
with a file server also being a print server, or an web server also
handling DNS. It's the "applications" that should have their own
servers. For example, a SQLServer shouldn't also be an Exchange server,
or a domain controller shouldn't also be a web server. "Can" you run it
all on one machine? Sure. Something like SBS even forces you to. But
"should" you is another question.
As I understand it the issue is that one rogue program can affect the others. No memory pooling, and no CPU quota.

Please correct me if I am wrong. This might be easily doable in the "server" editions, but I'd rather think that Microsoft wants to sell more Windows licenses.


This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.