oh, by the way... SQL 2016 SP1 CU5... we're still on CU5 just in the lab. We're on CU2 in production. CU3 Microsoft said "don't do it". CU4 we tried... and we got sql replication delays and issues with DRS. uninstalled CU4 and everything was fine. (but apparently we're the only ones that reported that issue). We haven't put CU5 in production yet. So... that said... "just in case" you think it MIGHT be the CU5; if you're going to try to downgrade to a different CU; downgrade to CU2. CU5 might be fine, tho.
On Thu, Sep 28, 2017 at 2:49 PM, Sherry Kissinger < sherrylkissin...@gmail.com> wrote: > We've seen sporadic Console slowness issues, "usually" seen when we have > Compatibility set to SQL 2016, and the person using the console is not a > 'full admin'. If we just for the cm_ database at the CAS (yes, we sadly > need a cas, with over 300k clients, we have to have one. :( ) , set it to > sql 2012 (not sql 2014, fyi, but that's just because we've never tested > that), and BAM! console slowness issues gone. > > We've tried various things with various success rates. One team member > spent WEEKS running, re-running, tweaking, adjusting, etc. etc. the Ola > Hallengren indexing scripts, and adjusting the timings, and trying more > frequent update statistics. sometimes it would help... and then a day or > two would pass, and although nothing had changed and the > reindexing/statistics had run just fine; console slowness again. So > again... back to sql 2012 compatibility. We keep trying, though. > > But honestly it's not like we spend every waking moment trying to get to > sql 2016 compatibility. It would be nice to have it; but since we can work > around the issue by bumping the CAS (and this is just the cas, we leave the > primaries at sql 2016 compat), down to sql 2012, we just live with it until > we get a spare moment to try again. > > On Thu, Sep 28, 2017 at 2:13 PM, Jason Sandys <ja...@sandys.us> wrote: > >> The slowdown is a result of RBA processing. The more complicated the RBA >> rules, the more noticeable the slowdown. No RBA = no slowdown. >> >> >> >> I think that article may have a typo in it. >> >> >> >> Changing the compatibility level is easy to do, easy to test, and easily >> reversed. >> >> >> >> J >> >> >> >> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.myitf >> orum.com] *On Behalf Of *Stuart Watret >> *Sent:* Thursday, September 28, 2017 11:42 AM >> >> *To:* mssms@lists.myitforum.com >> *Subject:* Re: [mssms] RE: Slow Console performance for some users >> >> >> >> for me it doesn’t explain the fact some people are fine, ill open a call >> tomorrow. >> >> >> >> On 28 Sep 2017, at 17:26, Daniel Ratliff <dratl...@humana.com> wrote: >> >> >> >> Its recommended to be set to 130 per the article yes, but that doesn’t >> mean you don’t have the issue. >> >> >> >> Find a culprit query, and run the instructions they gave to see if you >> are impacted. >> >> >> >> *Daniel Ratliff* >> >> >> >> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@ >> lists.myitforum.com <listsad...@lists.myitforum.com>] *On Behalf Of *Daniel >> Ratliff >> *Sent:* Thursday, September 28, 2017 12:03 PM >> *To:* mssms@lists.myitforum.com >> *Subject:* RE: [mssms] RE: Slow Console performance for some users >> >> >> >> Heres the details. https://support.microsoft.com/en-us/help/3196320/ >> sql-query-times-out-or-console-slow-on-certain-configuration-manager-d >> >> >> >> *Daniel Ratliff* >> >> >> >> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@ >> lists.myitforum.com <listsad...@lists.myitforum.com>] *On Behalf Of *Kent, >> Mark >> *Sent:* Thursday, September 28, 2017 11:38 AM >> *To:* mssms@lists.myitforum.com >> *Subject:* RE: [mssms] RE: Slow Console performance for some users >> >> >> >> We are running SQL2016 as well, the compatibility is set to 2016. So you >> are recommending dropping this down to 2012? Does this help address >> anything else? Just curious, thank you! >> >> >> >> Mark Kent >> >> Manager, Client Systems Engineering >> >> Technology Support Services >> >> Resources for Information, Technology and Education (RITE) >> >> http://rite.buffalostate.edu >> >> >> >> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@ >> lists.myitforum.com <listsad...@lists.myitforum.com>] *On Behalf Of *Jason >> Sandys >> *Sent:* Thursday, September 28, 2017 10:41 AM >> *To:* mssms@lists.myitforum.com >> *Subject:* RE: [mssms] RE: Slow Console performance for some users >> >> >> >> Change the compatibility level for the ConfigMgr database in SQL Server >> to SQL Server 2012 (110). There is a known issue that stems from a change >> in SQL Server 2014 and 2016 that hasn’t been accounted for (yet to my >> knowledge) in ConfigMgr. >> >> >> >> J >> >> >> >> -----Original Message----- >> >> From: listsad...@lists.myitforum.com [mailto:listsadmin@ >> lists.myitforum.com <listsad...@lists.myitforum.com>] On Behalf Of >> Stuart Watret >> >> Sent: Thursday, September 28, 2017 8:42 AM >> >> To: mssms@lists.myitforum.com >> >> Subject: Re: [mssms] RE: Slow Console performance for some users >> >> >> >> What I’m seeing in that log is sql execution delays, the same time his >> console is waiting. >> >> >> >> I do the same thing, navigate to the same package it’s almost instant. >> >> >> >> I click, I see a sql command and my console refreshes, he clicks, same >> command, no action. >> >> >> >> I may raise it with MS. >> >> >> >> I have the hot fix installed, so that doesn’t help. >> >> >> >> It’s the working for some, not others bit thats got me puzzled. >> >> >> >> S. >> >> >> >> >> >> >> >> > On 28 Sep 2017, at 14:18, Brucker, Chris <chris.bruc...@bankatfirst.com> >> wrote: >> >> > >> >> > We have been seeing similar issues since our upgrade to 1706 wave 1. I >> haven't made time yet to upgrade to wave 2 and the hotfix to see if that >> fixes it. >> >> > >> >> > Another theory I have wanted to test is how often are your hardware >> inventories, application evaluations, software update scans, etc occurring? >> I'm a bit of a spaz about that and have hardware inventories and software >> update scans every 12 hours. Application evaluations every 4 hours and >> Software inventories occur every 7 days. >> >> > >> >> > SQL has 4 cores and 24gb of ram, SCCM has 2 cores and 12gb ram. 2700 >> clients. >> >> > >> >> > Thanks, >> >> > Chris Brucker >> >> > >> >> >> On Sep 28, 2017, at 9:06 AM, Daniel Ratliff <dratl...@humana.com> >> wrote: >> >> >> >> >> >> CAUTION: The e-mail below is from an EXTERNAL source. Please do not >> open attachments or click links from an unknown or suspicious origin. >> >> >> >> >> >> >> >> >> >> >> >> Anything in smsprov.log? >> >> >> >> >> >> Daniel Ratliff >> >> >> >> >> >> -----Original Message----- >> >> >> From: listsad...@lists.myitforum.com [mailto:listsadmin@ >> lists.myitforum.com <listsad...@lists.myitforum.com>] On Behalf Of >> Stuart Watret >> >> >> Sent: Thursday, September 28, 2017 5:31 AM >> >> >> To: mssms@lists.myitforum.com >> >> >> Subject: [mssms] Slow Console performance for some users >> >> >> >> >> >> So, finished our migration to new server running 1706. >> >> >> >> >> >> OS 2016 / SQL 2016 Sp1 CU5 / Compatibility 130 >> >> >> >> >> >> Its absolutely fine for me, I have three colleagues who are also full >> admins, one of them is fine, the other two have appalling console >> performance. >> >> >> >> >> >> We have removed the console and reinstalled, we have had them run the >> console on the server, the results are the same. >> >> >> >> >> >> If they drill down to a package, then click the program tab, they have >> the donut of doom, for a long time before it enumerates. >> >> >> >> >> >> This is repeatable. >> >> >> >> >> >> Any thoughts? >> >> >> >> >> >> Stuart Watret >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> > >> >> > ********************************************************************** >> >> > The information contained in this message from First Financial Bancorp >> or its affiliates and any attachments are confidential. It is not intended >> for transmission to, or receipt by, anyone other than the addressee(s), or >> a person authorized to deliver it to the named addressee(s). If you have >> received this message in error, you are prohibited from copying, >> distributing or using the information. Please contact the sender >> immediately by return email and delete the original message. >> >> > >> >> > >> >> > >> >> > >> >> >> >> >> >> >> >> >> >> >> The information transmitted is intended only for the person or entity to >> which it is addressed >> and may contain CONFIDENTIAL material. If you receive this >> material/information in error, >> please contact the sender and delete or destroy the material/information. >> >> Humana Inc. and its subsidiaries comply with applicable Federal civil >> rights laws and >> do not discriminate on the basis of race, color, national origin, age, >> disability or >> sex. Humana Inc. and its subsidiaries do not exclude people or treat them >> differently >> because of race, color, national origin, age, disability or sex. >> >> English: ATTENTION: If you do not speak English, language assistance >> services, free >> of charge, are available to you. Call 1‐877‐320‐1235 <(877)%20320-1235> >> (TTY: 711). >> >> Español (Spanish): ATENCIÓN: Si habla español, tiene a su disposición >> servicios >> gratuitos de asistencia lingüística. Llame al 1‐877‐320‐1235 >> <(877)%20320-1235> (TTY: 711). >> >> 繁體中文(Chinese):注意:如果您使用繁體中文,您可以免費獲得語言援助 >> 服務。請致電 1‐877‐320‐1235 <(877)%20320-1235> (TTY: 711)。 >> >> Kreyòl Ayisyen (Haitian Creole): ATANSION: Si w pale Kreyòl Ayisyen, gen >> sèvis èd >> pou lang ki disponib gratis pou ou. Rele 1‐877‐320‐1235 >> <(877)%20320-1235> (TTY: 711). >> >> Polski (Polish): UWAGA: Jeżeli mówisz po polsku, możesz skorzystać z >> bezpłatnej >> pomocy językowej. Zadzwoń pod numer 1‐877‐320‐1235 <(877)%20320-1235> >> (TTY: 711). >> >> 한국어 (Korean): 주의: 한국어를 사용하시는 경우, 언어 지원 서비스를 무료로 >> 이용하실 수 있습니다. 1‐877‐320‐1235 <(877)%20320-1235> (TTY: 711)번으로 전화해 주십시오. >> >> >> >> >> The information transmitted is intended only for the person or entity to >> which it is addressed >> and may contain CONFIDENTIAL material. If you receive this >> material/information in error, >> please contact the sender and delete or destroy the material/information. >> >> Humana Inc. and its subsidiaries comply with applicable Federal civil >> rights laws and >> do not discriminate on the basis of race, color, national origin, age, >> disability or >> sex. Humana Inc. and its subsidiaries do not exclude people or treat them >> differently >> because of race, color, national origin, age, disability or sex. >> >> English: ATTENTION: If you do not speak English, language assistance >> services, free >> of charge, are available to you. Call 1‐877‐320‐1235 (TTY: 711). >> >> Español (Spanish): ATENCIÓN: Si habla español, tiene a su disposición >> servicios >> gratuitos de asistencia lingüística. Llame al 1‐877‐320‐1235 (TTY: 711). >> >> 繁體中文(Chinese):注意:如果您使用繁體中文,您可以免費獲得語言援助 >> 服務。請致電 1‐877‐320‐1235 (TTY: 711)。 >> >> Kreyòl Ayisyen (Haitian Creole): ATANSION: Si w pale Kreyòl Ayisyen, gen >> sèvis èd >> pou lang ki disponib gratis pou ou. Rele 1‐877‐320‐1235 (TTY: 711). >> >> Polski (Polish): UWAGA: Jeżeli mówisz po polsku, możesz skorzystać z >> bezpłatnej >> pomocy językowej. Zadzwoń pod numer 1‐877‐320‐1235 (TTY: 711). >> >> 한국어 (Korean): 주의: 한국어를 사용하시는 경우, 언어 지원 서비스를 무료로 >> 이용하실 수 있습니다. 1‐877‐320‐1235 (TTY: 711)번으로 전화해 주십시오. >> >> >> >> >> >> > > > -- > Thank you, > > Sherry Kissinger > > My Parameters: Standardize. Simplify. Automate > Blog: http://mnscug.org/blogs/sherry-kissinger > -- Thank you, Sherry Kissinger My Parameters: Standardize. Simplify. Automate Blog: http://mnscug.org/blogs/sherry-kissinger