search cancel

Slow response from tmBuildTargetDeviceCache and tmGetTargetDeviceCache


Article ID: 163185


Updated On:


IT Management Suite


These are some of the scenarios noticed with some customers:

  1. Customer reported that while trying to search for a computer name under Quick Run for any of their tasks is taking too long to load (some times more than one minute).
  2. As well while trying to drill-down to any of the already executed tasks from the list under Task Status is taking a long time to populate the computer list.
  3. If a user with limited rights tries to add a schedule to a computer to run a task, it usually times out or load after 1 hour.
  4. In some instances it even locked the Internet Explorer page.

After looking at the profiler trace, we identified that tmBuildTargetDeviceCache and tmGetTargetDeviceCache stored procedures were the main culprits. 

tmBuildTargetDeviceCache was taken in some instances up to 220762.7 ms for example. 


In this particular case the customer had too many obsolete resource types from previous installations, as well he had too many security groups causing the scoping checks to take too long.



This issue has been fixed with our ITMS 8.0 HF2 release. However, on other later releases, tmGetTargetDeviceCache stored procedure has received further improvements.

Attached to this article is a revised version of the stored procedure that will be included in Post-SMP 8.5 RU1 release.   This version eliminates scoping based on all possible objects and, instead, reduces the number of items down to just scoped collections only. This suggested change should work for 8.1 RU7, 8.5, and 8.5 RU1

Also, with our ITMS 8.6 RU1, a newer version of this tmGetTargetDeviceCache stored procedure has been released to address some issues with "Computer search in Quick Run option for job tasks is very slow."




tmGetTargetDeviceCachev3.sql get_app