Thanks, however I have seen a lot of SQL "Best Practices" that can really mess up SCCM, so unless I read them from Nelson, Thompson, or a MS/TechNet article I do not follow them. If this setting is important to SCCM, then the SCCM team should include it in the docs.
On Mon, Apr 4, 2016 at 3:56 PM, Daniel Dreier <[email protected]> wrote: > FWIW: https://support.microsoft.com/en-us/kb/2806535 > > Also, there’s tons of good stuff on Brent Ozar’s site like: > https://www.brentozar.com/archive/2013/09/five-sql-server-settings-to-change/ > > > > Obviously, blindly making changes is never a good thing! > > > > -Daniel > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Todd Hemsell > *Sent:* Monday, April 4, 2016 2:58 PM > *To:* [email protected] > *Subject:* [mssms] SQL Threads taking a dump > > > > MY SQL server kept dumping threads and locking up. > > After a call to MS we changed a 0 to a 1 and the issue went away. > > CPU usage went form 100% to about 35% > > > > The setting is MAXDOP. Apparently if it is set to 0 SQL executes queries > across all processors in parallel. When it gets a block, it blocks all > processors. > > > > Setting it to 1 makes it run 1 query on 1 processor allowing up to 8 > queries to run at once. > > The SQL guy said he saw many cases of this nature in the SCCM queue. > > > > It is not in the documentation or any TechNet article or MS KB ... > Grrrrrrrr. > > > > This is what we changed. I am in no way advocating this, just an FYI. I > had never heard of it before. > > > > > > > > > > >
