Performance problems with SMS in MMC

[akloster]

I've inherited the maintenance of the SMS SQL 7 database and users (help desk guys) are complaining that interfacing with SMS in the MMC is slow, so I checked, and sure enough, it seemed slow to me too. (when expanding items in the tree structure, etc)&nbsp;&nbsp;I was wondering if anyone had any guidance, resources or tips for improving SMS performance.&nbsp;&nbsp;Anyone else have this problem?&nbsp;&nbsp;The users indicated that it had &quot;always been this way&quot;, do you think they will just have to live with this.<br><br>Thanks for any help.<br><br>Andrew

 

[Trunk]

Since the MMC pulls info from the site server, a lot depends on the amount of memory installed on the site server as well as the speed of the processor(s).&nbsp;&nbsp;It may be that you need to add memory to the site server, add faster processors, etc. <p>Tom Thaden<br><a href=mailto:thadents@usano.ksc.nasa.gov>thadents@usano.ksc.nasa.gov</a><br><a href= > </a><br>

 

[Jpoandl]

I am having the same problem with SMS SP2 on SQL 7.0 server.&nbsp;&nbsp;It seems that when our help desk attempt to user the MMC, our performance is very slow.&nbsp;&nbsp;(We have just migrated from LANDESK to SMS.&nbsp;&nbsp;LAndesk performance was much much better.)<br><br>I don't think it is a hardware problem.&nbsp;&nbsp;Our SMS site server is on a dual Xeon III 800 with 512MB of memory.&nbsp;&nbsp;Even our hard disks are high performance 10K RPM.&nbsp;&nbsp;Our site currently has only 25 client machines in the database.&nbsp;&nbsp;I would expect performance to be much greater.<br><br>Does anyone have any suggestions?<br><br><br>

 

[Jpoandl]

Update:<br><br>Listed above describes the performance issue's I was having with SMS Remote Tools and inventory.&nbsp;&nbsp;(Basically it took over a minute to initiate contact with a remote client. It should take between 5 and 15 seconds on a LAN.)<br><br>Anyway, I called Microsoft about this issue.&nbsp;&nbsp;After hours upon hours of trouble shooting, we finally figured out what the problem was.&nbsp;&nbsp;<br><br>It turns out that because our SMS2.0/SQL 7.0 server was installed on a DUAL processor system, SQL was utilizing both processor for SQL functions.&nbsp;&nbsp;(This is what I would expect) However, Microsoft told me to configure SQL 7.0 to utilize on one processor...instead of both.&nbsp;&nbsp;When I did this, the Remote Tools response time was much much faster...10 to 15 seconds.<br><br>Microsofts explaination was that when SQL 7.0 uses two processors at ton of overhead is generated.&nbsp;&nbsp;However, when the database grows bigger, we may find that by enabling both processors we may get better performance.<br><br>hope this helps.