We have a SCCM 2012 environment set up on our test network. Everything is virtual. I have a VM that has a primary site and VM that is a remote SQL server. Both are running Server 2008 R2. It has been running for a few month now and I have not had any issues with console speed until now. When I try and look at updates in an update package, it will take about a half hour to display the 250ish updates that are in that package. The CPU on the Primary site server is running below 10% and the RAM is running right at half. At the same time while SCCM is looking up the results the SQL box jumps to about 25% CPU and the RAM stays steady at about half as well. There are a couple other things on this SQL VM and it has 12 GB of RAM. I also see this behavior when searching all updates, and general movement around the console. I have a maintenance task set up in SCCM to rebuild indexes every Saturday. There are only 80 clients inside of this test environment. What could cause this? Any ideas on how to fix it?

Have you tried enabling the task ev

I'll change it to run every night. We went a few months without it turned on at all. I enabled the to run once weekly thinking that might speed things up and it hasn't.

Set it to run every night. It should have run last night sometime between 7pm and 11:59pm. No improvement on speed this morning.

See smsdbmon.log if it ran at all.
Slow performance might also be caused by numerous other things (disk i/o, RAM, paging, etc). You should use perfmon.exe to get an ideda about the overall state of the system.

The log said reindexing completed. Things look fine on the performance side. The VM running Configuration manager is a bit over powered and the VM running the SQL stuff seems to be about right. If I want to look in update packages, update groups, or at all updates it is still extremely slow.

For example, there are 998 updates when this screen would finally load. It takes almost a half hour to populate the list. If I try and look at these and go somewhere else like administration it bogs the console down to an unusable state unless you let it sit there for a half hour or restart the Configuration Manager server to break the query.

It's a vm, right?  (both boxes)?  the one with the provider, and the one with sql?  Is it possible.... that until this issue started happening, your boxes were the only ones on the underlying infrastructure?  I.e., NOW you are sharing the underlying disk and/or cpu and/or RAM with other servers--and you weren't before?  and those other VMs are taking all your disk i/o (or ram, or cpu)

Check with the group that does the VM provisioning--and see if changes were made to your underlying resources.  I'll guess *they* (the big evil *they* in the sky) determined that you didn't need all those resources--and gave them to someone else.

We have not changed our underlying infrastructure or added anything new to our hosts. I do all my own provisioning. Our entire IT department has 4 techs and 3 programmers so there aren't the departmental issues of getting resources provisioned. I could just add more CPU but I don't see that as a fix if it was not behaving this way before.

Yes, I know this is an old post, but Im trying to clean them up. Did you solve this problem, if so what was the solution?

Im going to echo the statements above this is likely to be a IO issue with the disk subsystem. You will need to look at you Physical host to see if there is anything issue with items like disk query length (should be zero), to much paging, etc.