Best Practices for Dashboards and Layouts

you can improve ivanti service manager performance by following the dashboard and layout best practices described in these sections dashboard best practices docid\ sbo1vaw3dlfphcg 9c4splayout best practices docid\ sbo1vaw3dlfphcg 9c4sp dashboard best practices because dashboards are created from multiple dashboard parts, they usually execute multiple saved searches when they are opened or updated you can significantly improve performance by following these best practices ensure that dashboards display only active records, and that searches configured in dashboard parts do not search for closed or completed records disable or increase the duration of automatic refresh on all active dashboard parts use the fewest possible dashboard parts to create a dashboard (no more than four whenever possible) wherever possible, add date filters and remove the all option wherever possible, remove memo fields from grids enable auditing only when necessary layout best practices ensure that tabs in a workspace exist only if they are absolutely necessary workspace tabs that contain counters can consume significant resources if a tab contains a counter, ivanti service manager executes a query to return the number of records available on that tab each tab that generates a query adds to the time it takes for the parent workspace to load improving back end processing this section describes how to tune stored procedures, triggers, and file import processes to improve performance stored procedures and triggers docid\ sbo1vaw3dlfphcg 9c4spfile import processes docid\ sbo1vaw3dlfphcg 9c4sp stored procedures and triggers we recommend that you configure stored procedures and triggers outside of ivanti service manager to avoid any unnecessary problems stored procedures often consist of complex searches that query multiple database tables a deadlock can result if a stored procedure is scheduled to run too frequently wherever possible, minimize the use of frequently scheduled stored procedures and triggers that query primary business objects such as incident, problem, change, journal, task, and other primary business objects if possible, do not run these procedures at intervals of less than five minutes if a frequently scheduled stored procedure is necessary, we recommend that you run it outside of normal business hours file import processes if there are too many files to process or import in too short of a time (which might occur if the creation of a new record generates multiple queries), system performance can be significantly impacted wherever possible, schedule the file import process to run outside of normal business hours using event and error log files for troubleshooting microsoft event logs and message queuing error logs are often helpful in determining common configuration errors, especially with regard to the email listener and file import process we recommend that you review these logs when you troubleshoot performance issues