Agreed... I think it should be one of those things (I'll try to remember) to tell new CM admins regarding SQL. Right now I usually remember to say "remember you want 'Simple' Recovery and be sure to cap how much memory SQL is allowed to have, so you leave some for CM itself". I should make that a list of 3 things "And Ola's script--everyone needs that, Period, don't even ask why."
Sherry Kissinger On Thursday, July 10, 2014 1:15 PM, "Lindenfeld, Ivan" <[email protected]> wrote: Strong endorsement for Ola’s script. It’s so good our DBA’s stole it. Ivan Lindenfeld FNF Jacksonville From:[email protected] [mailto:[email protected]] On Behalf Of David O'Brien Sent: Thursday, July 10, 2014 9:22 AM To: [email protected] Subject: RE: [mssms] SCCM 2012 Indexing issue Implement Ola's solution for SQL, you'll very likely notice some improvement after that. Don't rely on the built-in task. Sent from my Windows Phone ________________________________ From: Daniel Ratliff Sent: 10/07/2014 10:25 PM To: [email protected] Subject: RE: [mssms] SCCM 2012 Indexing issue I will confirm with our admins, but we have had SQL issues all week and I think upgrading SQL 2012 to SP2 resolved all of our issues. Daniel Ratliff From:[email protected] [mailto:[email protected]] On Behalf Of HELMS, DAVID C Sent: Thursday, July 10, 2014 8:20 AM To: [email protected] Subject: [mssms] SCCM 2012 Indexing issue I am having very poor performance within our SCCM console (software updates) and other issues like running reports via SSRS. I have found several sites talking about how the SQL maintenance for rebuilding indexes isn’t working like it should and this is likely the root cause. I found the following link that others referenced to rebuild the indexes, but I’m not a SQL guy so I’m a little unclear on what all I should do. http://ola.hallengren.com/sql-server-index-and-statistics-maintenance.html Is anyone experienced these types of issues and if you would share how you were able to resolve this. 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. ________________________________ NOTICE: The information contained in this message is proprietary and/or confidential and may be privileged. If you are not the intended recipient of this communication, you are hereby notified to: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately.
