ealdrich
Posts: 341
Score: 9 Joined: 6/1/2001 Status: offline
|
Well in the famous words of Bill Anderson, "It depends!" :-) Our position is that one should not install our SQL components *on* the SMS/CfgMgr site server, but instead offload its transaction processing onto a separate SQL/IISbox... Now, whether or not you install onto an existing SQL farm, and split IIS off to a separate web farm... place this on an existing SQL/IIS system supporting other SQL/web apps, or stand up a dedicated SQL/IIS box just for this, is all entirely up to you. We support any combination of the above... we just prefer that you not piggy-back on top of your CfgMgr central site server for example, just "because" it already has SQL/IIS there for CfgMgr (also suspect you could get in a jam on SQL licensing as well if you did so)... rationale for this recommendation: we have no clue what kind of horsepower is already in place on your central, if it's loafing along 24x7 at 10% cpu or 90% cpu... our solution can get intense relative to transaction processing in a large estate, so we really prefer you treat this like any other business critical SQL app, and host it accordingly. Hope that makes sense...
_____________________________
Ed Aldrich | Solutions Engineer | 1E Inc Mobile: (401) 924-2293 US/Canada Toll Free: (866) 592 4214 Ed.Aldrich@1e.com | www.1e.com SMS/CfgManager (2003-2009) myITforum Advisory Council and Columnist New England Area SMS User Group Facilitato
|