Smart IT performance tuning recommendations
This topic describes performance tuning recommendations for the following components:
Centralized configuration
Recommendations for global search
To improve global searches, the following values were set in the Centralized configuration after upgrade. These values are set by default during a fresh install.
| Configuration parameter | Value |
|---|---|
| isExclude_TAG_and_CI_ID | true |
| useLeadingSearchForAsset | true |
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 position | Field ID | Field name |
|---|---|---|
| 1 | 1000003231 | ASLOGID |
| 2 | 7 | STATUS |
On the WOI:Workorder form, composite index 100003231_1 was added:
| Column position | Field ID | Field name |
|---|---|---|
| 1 | 100003231 | ASLOGID |
| 2 | 7 | STATUS |
Also refer to the following the knowledge article for index recommendations to support console searches:
https://selfservice.bmc.com/casemgmt/sc_KnowledgeArticle?sfdcid=kA214000000d8UZCAY&type=Solution
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 position | Field ID | Field name |
|---|---|---|
| 1 | 400130900 | Source.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.
Comments
The AR System FTS Settings (Link to Community Doc) is only for older versions. Please update the documentation!
Hello Matthias,
Thanks a lot for your comment.
Our performance team will update this.
Regards,
Nilay Agambagis
The parameters "isExclude_TAG_and_CI_ID" and "useLeadingSearchForAsset" are no longer defined in the Smart IT database but in the global settings ( * ) of com.bmc.arsys.smartit component of ar system server. See following link: https://docs.bmc.com/docs/smartit1808/configuration-parameters-for-smart-it-818731786.html
Regards Patrick
Hello Patrick,
Thank you for your comment. We are communicating with the SME about this. We will get back to you soon.
Thanks,
Dhanya Menon
Hello Patrick,
Thanks for your comment.
I have changed the location of the configuration parameter to Centralized configuration.
Regards,
Nilay Agambagis
Is FTS Fortification really needed since Version 18.xx? ITSM 9.1+ is optimized for FTS and SmartIT 18.xx needs ITSM 18.xx
Hello Stefan,
Thank you for your comment. We are communicating with the SME about this. We will get back to you soon.
Thanks,
Dhanya Menon
Hi Stefan,
We have updated this page and removed the section about FTS Fortification.
Thanks,
Dhanya