Index Creation on extended tablesSummaryThis article provides information on when you cannot see the index created after creating an index via Tables & Columns. The reason could be that the table is extended from another table; for example, cmdb_ci_kvm_storage_pool extends from cmdb_ci, which extends from CMDB. In this case, the index will be created on cmdb (or cmdb$par1, depending on where the column is.) In this case, we need to check the Storage Column Alias (sys_storage_alias). TIP: Before adding an index, check if one has already been created. By default, if one has already been created, the platform will not try to create a new one.ReleaseAll releasesInstructionsHere are the steps to check: 1. Create an index on extended tables (for example, cmdb_ci_kvm_storage_pool) 2. We go to the tables to check if the index is present on the table (in this case, it will not be present): 3. The next step is to go to Storage Column Alias (sys_storage_alias) and find the column. In this table, we will see which physical table our column is present in (in this example, it is on cmdb$par1 and has the name a_int_14). 4. If we check in Tables for cmdb$par1 (it is better to search). 5. We can see that the index is present: