This documentation supports the 1.4 version of Remedy with Smart IT.

To view the latest version, select the version from the Product version menu.

Smart IT performance tuning recommendations

This topic describes performance tuning recommendations for the following components:

AR System server

BMC Remedy with Smart IT utilizes a significant amount of FTS searching. It is critical that you apply the FTS Fortification fix to reduce CPU usage on the AR Server and achieve optimal performance and scalability. For more information on the FTS fortification fix please refer to the following BMC Communities blog:

https://communities.bmc.com/community/bmcdn/bmc_atrium_and_foundation_technologies/bmc_remedy_ar_system/blog/2013/08/30/the-pulse-fts-fortification

BMC also recommends that you set the FTS threshold to 2000 to improve Smart IT searching performance.

BMC Remedy ITSM MSSQL and Oracle database

The following indexes are common to both MSSQL and Oracle databases.

Recommendations for the Ticket Console

The following indexes were added to improve performance and will be provided in the next service pack for the current release of BMC Remedy IT Service Management (ITSM) and incorporated into the next full release.

On the SRM:Request form, composite index 1000003231_1 was added:

Column positionField IDField name
11000003231ASLOGID
27STATUS

On the WOI:Workorder form, composite index 100003231_1 was added:

Column positionField IDField name
1100003231ASLOGID
27STATUS

Also refer to the following the knowledge article for index recommendations to support console searches:

https://kb.bmc.com/infocenter/index?page=content&id=S:KA402577

These index changes have been incorporated into the product starting in BMC Remedy ITSM 8.1 SP2.

Recommendation for displaying asset details

The following index was added to improve performance and will be provided in the next service pack for the current release of BMC Remedy ITSM and incorporated into the next full release.

On the BMC.Core:BMC_BaseRelationship form, index C400130900_1 was added:

Column positionField IDField name
1400130900Source.ReconciliationIdentity

There should be a delivered index on Destination.ReconciliationIdentity. Depending on your release, there might not be an index; in that case, create one.

Recommendations for Collision and Calendar request

When creating change request, if you notice that the SQL query is taking high response time for Collision and Calendar request, you can apply the following index to improve performance. You might experience performance issues if you are using BMC Remedy ITSM version prior to 9.1 Service pack 1 (9.1.01). This index will help you to avoid full table scan for the table 'CHG:Infrastructure Change'.

On the CHG:Infrastructure Change form, create a non-unique index on the field Scheduled End Date.

From BMC Remedy Developer Studio, create an overlay of the CHG:Infrastructure Change form, and add an index on the field Scheduled End Date.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments