Hi Dale,
You will probably get loads of answers.
Firstly, it is more than technically possibly and I would say that in some instances it actually makes sense. I am not saying in yours it does but it could. On Dev / Test it's almost always the same machine and for production.. its usually only separate
because the SQL is used for more than 1 "application tier".
1) Security of the Data
Depending on what data you even have (PII, HBI, MBI etc), you may not want a service running on your machine that requires non-SQL admins to publish files and or data. You may end up with some security holes. Will it for sure, no but it's more likely as
they are on the same machine (using the same memory etc too). Yes Yes different memory spaces, but physically.. still the same
However at the same time, I've had systems running IIS, BizTalk and SQL all on the same box SPECIFICALLY because we needed it to be sequestered from everything else on a private network and the machine itself was specifically large and intended for that
purpose.
2) Performance. Really depends here. If you truly have a large box, and your traffic is not... super huge (I mean millions of page views etc a day), then...honestly buying two machines is a waste of time and money. (note you should at least have some
type of VM backup :-) )
3) Supportability. What is your backup / recovery / maintenance etc that you must follow. How does that impact the fact (if at all) that they are together.
I've been doing this stuff for over 20 years and personally I have no issue with them on the same box. Especially if the box is large enough for it.
Other than personal preference, there is no technical reason you cannot run them together. There is also no specific set of reasons that I can think of NOT to run them together.
BizTalk, CRM, IIS, VSTF and even SharePoint can all be configured on a single system. And in many cases, while it's only done for Dev / Test, I've seen plenty of businesses whom don't have the resources to buy systems to run one system.
The biggest problem is if you have to have multiple "admins" or people touching the machine, and now all of a sudden you have all these remote sessions and people being goofy, rebooting, patching incorrectly etc etc and impacting the other "technology"
stack.
-
Edited by
Anokneemous
11 hours 6 minutes ago
Updated Detail