J.4 Performance Tips for the Inventory ConsoleOne Utilities

This section discusses the performance tips for the Inventory ConsoleOne utilities:

NOTE:If the Inventory ConsoleOne utilities are retrieving data from a large database, you must stop the Storer service before running the utilities. This improves the performance of the ConsoleOne utilities.

If your database is huge, ensure that the machine running the Inventory ConsoleOne utilities has at least 5 GB free hard disk space.

J.4.1 Inventory Reports Performance Tips

If you have more than 1000 inventoried servers in your database, listing all of the subreports consumes time. We recommend that you specify the list of subreports. By doing so, the general performance of the reports is improved.

J.4.2 Inventory Data Export Performance Tips

  • To maximize the performance of Inventory Data Export, you need to enable the filter condition in DBExport. Based on the query you specify, DBExport exports only selected software.

  • During export, deselect the attributes that you do not want to use. To do this, use the DBExport and the Required Attributes Only option.

  • Perform the software export separately. This greatly improves the performance of the Non-Software Export function.

J.4.3 Inventory Query Performance Tips

  • Specify queries using the AND condition in multiple groups to increase performance.

  • Split a complex query with several logical operators into multiple groups separated by a logical operator.

  • If you want to use a complex query, increase the database cache size. For more information on tuning databases, see Section J.1, Database Parameter Tuning Tips.

  • Save fast, narrowed-down queries for future use.

  • Do not invoke the Inventory Query by connecting to a database over a slow link.

  • If a complex query takes more than 10 minutes to execute over a fast link, you probably do not have any inventoried servers that match the query you specified. The following message is displayed:

    No Computer system matched the query
    

    Close the Result window, narrow your input query and retry. Repeat the process of narrowing your query until you locate your inventoried servers.

  • For optimal performance, we recommend that you do not use more than four groups and not more than three logical operators separating the four groups in your query.

  • If you know the exact logical string, avoid using the MATCHES operator. The MATCHES operator searches the database for a result based on the pattern you specify. This results in performance degradation.

  • If you want to check for a particular inventory component not stored in the Inventory database, use the (ISNULL) operator instead of a query with a regular attribute.