KNOWN ISSUE: vComputer needs performance optimization
Last Updated May 20, 2013
vComputer uses outer joins to Inv_AeX_AC_Primary_User and Inv_AeX_AC_TCPIP, which are often not accessed/needed in queries that do need vComputer.
In large databases, using vComputer can cause a slow results return, specially when trying to access Computer information.
This issue has been reported to the Symantec Development team. A fix is already available with the ITMS 7.1 SP2 MP1 Release (See DOC6052 under fixed issue #15).
Dev optimized this view so that on a large database rather than taking almost 2 seconds to run the query to populate areas like a Task target builder initial view, it takes less than a second, or approximately half the time.
Using outer apply, in conjunction with the "top 1 ... order by" requirement of the existing subselects, allows the query optimizer to skip these when not needed, which is very frequently, while keeping the same functionality/compatibility.
Workarounf for ITMS 7.1 SP2: The following change has been suggested as a workaround for now for customers that are still using ITMS 7.1 SP2. Please download 'Fix_eTrack2751863_vComputer_Optimized.sql' and run it in the Microsoft SQL Management Studio against the Symantec Management Platform database.