SOLVED Painfully Slow SCCM Console in Application Management

[walthers]

Hello Everyone,

Ive exhausted all common research and troubleshooting steps I know of.

Like the title says, the SCCM Console is extremely slow to respond, especially under Application Management. Searching for an application works reasonably quick, but trying to further interact with any application, will send you waiting for up to a Minute, until the Deployment Types load in, or you are able to right click the app for more options.
The same happens for Assets, generally searching / browsing through collections is okay, as soon as you want to view properties or details, the waiting begins.
Other things in the console, like Updates, OSD or Administration work fine, and all properties can be accessed without delay.

Has anyone experienced similar or knows this issue?

The problem started more or less suddenly, with no (for me) obvious reason (like Updates or Hardware).

Any help would be very appreciated.

 

[Garth]

Have you confirmed that SQL is healthy? Have you confirmed that WMI is not overloaded? Have you checked the network?
When did you last index your database?

 

[walthers]

Thanks for your reply.
The SCCM Server is an all-in-one installation, therefore no problemwith networking.
Hardware utilization is minimal.
As for DB indexing, I thought about implementing this script by Ola Hellagren, but havent done so yet.
Im not sure if this would make such a big difference on a problem that happended so suddenly.
If nothin else helps, I would also try this Option.

Any more ideas as for what to check?

 

[Garth]

Thanks for your reply.
The SCCM Server is an all-in-one installation, therefore no problemwith networking.
Hardware utilization is minimal.
As for DB indexing, I thought about implementing this script by Ola Hellagren, but havent done so yet.
Im not sure if this would make such a big difference on a problem that happended so suddenly.
If nothin else helps, I would also try this Option.

Any more ideas as for what to check?

if you have not done Ola script, I would start there before doing anything else.

 

[walthers]

Alright, Index Optimization is now implemented in the SQL DB.
It actually helped a lot. I would say, its about 90% back to as it where before.
Are there any more tips to get it a bit more snappy?
If not, I'd say its solved. Thanks again for the tip.

 

[Garth]

Make sure you do the optimization daily.
The rest will depend a lot of WMI and how overload it is.

 

[Hoa Le]

Alright, Index Optimization is now implemented in the SQL DB.
It actually helped a lot. I would say, its about 90% back to as it where before.
Are there any more tips to get it a bit more snappy?
If not, I'd say its solved. Thanks again for the tip.

I'm a beginner and am having the same error as you. Query time from console is very slow. Can you help me on how you did it?

 

[Garth]

I'm a beginner and am having the same error as you. Query time from console is very slow. Can you help me on how you did it?

did you optimize the dB? https://www.recastsoftware.com/reso...-hallengrens-sql-server-maintenance-solution/

 

[walthers]

Unfortunately, the behavior is back to its original slowness.
After implementing the index optimizations, it was working well for a while, but it gradually got slower.
I tried scheduling the SQL optimization weekly, daily, and even every few hours, but there are no more improvements in the console.
When interacting with the SCCM PowerShell, everything is snappy (getting Application Information, creating deployments, etc.), and as quick as you'd expect. But doing it manually in the console...

Does anyone have any ideas what could be the issue here?
It's really no fun waiting minutes after every click :/

 

[Garth]

Unfortunately, the behavior is back to its original slowness.
After implementing the index optimizations, it was working well for a while, but it gradually got slower.
I tried scheduling the SQL optimization weekly, daily, and even every few hours, but there are no more improvements in the console.
When interacting with the SCCM PowerShell, everything is snappy (getting Application Information, creating deployments, etc.), and as quick as you'd expect. But doing it manually in the console...

Does anyone have any ideas what could be the issue here?
It's really no fun waiting minutes after every click :/

By chance do you have two providers?

 

[Bob Hatcher]

Thanks for your reply.
The SCCM Server is an all-in-one installation, therefore no problemwith networking.
Hardware utilization is minimal.
As for DB indexing, I thought about implementing this script by Ola Hellagren, but havent done so yet.
Im not sure if this would make such a big difference on a problem that happended so suddenly.
If nothin else helps, I would also try this Option.

Any more ideas as for what to check?

I had problem very similar to this. I ended up doing a SQL Re-Build of the CM_XXX database during a scheduled downtime for the system as this requires the SCCM to be offline, I do it on a Sunday and I have had no issues since.

 

[walthers]

By chance do you have two providers?

No, the SCCM as well as its DB are installed on the same Server. Single purpose, no othere services besides it.

I had problem very similar to this. I ended up doing a SQL Re-Build of the CM_XXX database during a scheduled downtime for the system as this requires the SCCM to be offline, I do it on a Sunday and I have had no issues since.

That sound promising, could you elaborate further what you had to do in order to perform that rebuild?
Maybe you have the guide / instuctions you used?

 

[Garth]

Tôi đã làm điều này nhưng nó vẫn không thay đổi. Máy chủ phản hồi rất chậm. Có điều gì tôi chưa thử không?

What do the logs say is causing the slowness? e.g. what take all the time?

 

[Bob Hatcher]

No, the SCCM as well as its DB are installed on the same Server. Single purpose, no othere services besides it.

That sound promising, could you elaborate further what you had to do in order to perform that rebuild?
Maybe you have the guide / instructions you used?

Here is what I use.
Open SQL Server Management Studio.
Click on Management
Right-Click on Maintenance Plans
Select Maintenance Plan Wizard then Next once the wizard opens.
Type some descriptive name: I use "Re-Build Index CM_XXX (Sun and Weds)"
Go down to Schedule and set Frequency to Weekly Sun and Weds
Pick a good time that you know will not affect users i.e.: Midnight
Click on OK
Click on Next
Under Select Maintenance Tasks I selected the checkboxes for Check Database Integrity, Shrink Database, Rebuild Index, and Clean up History.

Under Rebuild Index Task do not check Keep Index Online​

A summary of what you chose will show. Click next.

Each checked selection will open a separate window for details.​

Select from Databases: Usually CM_XXX and SUSDB and click on OK and then Next
repeat ...
PRETTY MUCH COMMON SENSE FROM HERE.
At the Complete the Wizard select Finish.
I would recommend during a time no one is using the SQL database to manually run this one time. If there is an error it will show up. If this is the first time allow several hours for the first time. If it passes with no errors then try out your SCCM console. If that made a difference you are good. If not get a DBA to help out. I hope this helps.

 

[vacationjason]

Thanks for your reply.
The SCCM Server is an all-in-one installation, therefore no problemwith networking.
Hardware utilization is minimal.
As for DB indexing, I thought about implementing this script by Ola Hellagren, but havent done so yet.
Im not sure if this would make such a big difference on a problem that happended so suddenly.
If nothin else helps, I would also try this Option.

Any more ideas as for what to check?

Hi what script are you talking about? I am experiencing the same thing in my own console.

 

[Garth]

Hi what script are you talking about? I am experiencing the same thing in my own console.

You can get more detail about Ola script here. https://www.recastsoftware.com/reso...-hallengrens-sql-server-maintenance-solution/