One of the best arguments to keep them away from SQL... If it sits on their server it chews up resources that you have to pay for (cpu licensing) If it is on a dedicated server there is no SQL licensing costs as SCCM is licensed as "SCCM with SQL technology"
Once I pointed that out to management all system center products got kicked off of the prod sql clusters. SCOM and SM moved to a server and mine stayed local. On Thu, Sep 8, 2016 at 8:55 AM, Olsson Mats (4004) < [email protected]> wrote: > I had the same discussion with “my” database admins who wanted to have the > database in their cluster to keep the number of DB servers down. > > After we installed a SP or CU to SCCM that restarted the database instance > without prior warning (it probably was in the documentation) the DB admins > rather quickly changed their minds about having SCCM together with line of > business apps in the same DB instance… > > Another thing to be aware of is that SCCM has it’s own list of supported > SQL versions and SP:s. It might be an issue if the DB admins wants to > upgrade and SCCM doesn’t support that version > > > > We installed a dedicated SQL on the primary site system instead and it has > been working well for 4-5 years now. > > *From:* [email protected] [mailto:listsadmin@lists. > myitforum.com] *On Behalf Of *Garth Jones > *Sent:* den 8 september 2016 14:19 > *To:* [email protected] > *Subject:* [mssms] RE: Configuration Manager Local SQL Best Practice > Documentation > > > > Let put it this way, for 400,000 computer Microsoft will NOT say if SQL > should be local or remote. Which BTW, SQL is hosted locally on a site with > 400,000 computers too. The Admins of that site are on this list too. J > > > > Like John said no MVP will say that you should put SQL remote, Heck if I’m > doing the install and SQL is remote, I add 15 days to the project due to > all the headache that arise from remote SQL. > > > > > > > > > > > > > > Garth Jones > > Chief Architect > > > > *www.Enhansoft.com* <http://www.enhansoft.com/> > > [image: Description: Description: cid:[email protected]] > <http://www.enhansoft.com/> > > *Enhancing Your Business* > > [image: Description: Description: Description: Description: Description: > Description: Description: cid:[email protected]] > <http://www.enhansoft.com/blog>[image: Description: Description: > Description: Description: Description: Description: Description: > cid:[email protected]] <https://twitter.com/enhansoft>[image: > Description: Description: Description: Description: Description: > Description: Description: cid:[email protected]] > <http://www.facebook.com/EnhansoftInc>[image: Description: Description: > Description: Description: Description: Description: Description: > Description: Description: Description: Description: Description: > Description: Description: Description: Enhansoft's YouTube Page] > <http://www.youtube.com/user/Enhansoft/videos>[image: Description: > Description: Description: Description: Description: Description: > Description: cid:[email protected]] > <http://myitforum.com/myitforumwp/community/groups/enhansoft/> > > > > *Subscribe to Enhansoft’s Newsletter! <http://www.enhansoft.com/register>* > > > > *From:* [email protected] [mailto:listsadmin@lists. > myitforum.com <[email protected]>] *On Behalf Of *Johns, > Damon (DoJ) > *Sent:* Wednesday, September 7, 2016 11:27 PM > *To:* [email protected] > *Subject:* [mssms] Configuration Manager Local SQL Best Practice > Documentation > > > > Hi Everyone, > > > > Can anyone point me to the Microsoft TechNet documentation where they > recommend that SQL be installed locally where a Primary Site has 50,000 > clients or less? I’ve found a couple of blogs where people mentioned this > but nothing specific from Microsoft. > > > > I’ve also found a number of blogs where MVP’s strongly recommend this, but > again nothing from Microsoft directly or the Configuration Manager team. > > > > There must be something out there!? > > > > Cheers > > Damon > > > ------------------------------ > > > CONFIDENTIALITY NOTICE AND DISCLAIMER > The information in this transmission may be confidential and/or protected > by legal professional privilege, and is intended only for the person or > persons to whom it is addressed. If you are not such a person, you are > warned that any disclosure, copying or dissemination of the information is > unauthorised. If you have received the transmission in error, please > immediately contact this office by telephone, fax or email, to inform us of > the error and to enable arrangements to be made for the destruction of the > transmission, or its return at our cost. No liability is accepted for any > unauthorised use of the information contained in this transmission. > > > > > >
