I have SCSM 2010 environment with a DB server and SM server.

The SM console is very slow in executing all queries and displaying results.

I identified that my SCSM DB server is very slow. Particularly the instance where the SCSM db is running. If I stop this instance, the server is very much normal.

IF the instance is running, its memory utilization is at peak.

I queried about the memory consumed by each db and found that Tempdb is utilizing most of the memory. Its DATA size is 60 GB and log size is 90 MB.

No problem with Disk free space as I have enough still free.

What is the best method to make my SM db works fast? Do I need to reset my SM database and start from scratch?

Or do I need to truncate incidents?(currently the running number is 22000 and I have only Incident management implemented).

Any help appreciated.

Hi,

You can check this post : http://www.systemcentercentral.com/faq-a-collection-of-tips-to-improve-service-manager-performance/

It's for SCSM 2012 but it can help you to improve SCSM performance.

try to add additional Tempdb using the same name and add 1 with the same initial size

make sure to back up in case of disaster.

There are a couple of things you can check.
What is the page life expectancy on the SQL Server.  Anything below 500 and you've got a problem.
Also, is the SQL Server running on a Virtual Machine?  If so, what is process queue.  If it is consistently high, that is a problem.
Are you running the Data Warehouse and the Command DB on the same instance?  That can cause performance issues.

• Edited by Foothill1 17 hours 49 minutes ago

There are a couple of things you can check.
What is the page life expectancy on the SQL Server.  Anything below 500 and you've got a problem.
Also, is the SQL Server running on a Virtual Machine?  If so, what is process queue.  If it is consistently high, that is a problem.
Are you running the Data Warehouse and the Command DB on the same instance?  That can cause performance issues.

• Edited by Foothill1 Friday, April 11, 2014 4:50 PM

There are a couple of things you can check.
What is the page life expectancy on the SQL Server.  Anything below 500 and you've got a problem.
Also, is the SQL Server running on a Virtual Machine?  If so, what is process queue.  If it is consistently high, that is a problem.
Are you running the Data Warehouse and the Command DB on the same instance?  That can cause performance issues.

• Edited by Foothill1 Friday, April 11, 2014 4:50 PM

There are a couple of things you can check.
What is the page life expectancy on the SQL Server.  Anything below 500 and you've got a problem.
Also, is the SQL Server running on a Virtual Machine?  If so, what is process queue.  If it is consistently high, that is a problem.
Are you running the Data Warehouse and the Command DB on the same instance?  That can cause performance issues.

• Edited by Foothill1 Friday, April 11, 2014 4:50 PM

Yes. The Tembdb movement did the trick.

After stopping the instance, I altered the database location to a different partition (not even different disk mind you)

and after restarting the instance, it created a new Tempdb file in the new location. This new file is just 32 MB. Also reduced my SQL RAM utilization from 7 gb to 2.5 gb.

all my SCSM services runs but with even much better speed while executing the queries.

Thanks to all..