Toad World® Forums

Toad for Oracle compare index comparison

Ok, this has occured in multiple versions since I started using Toad for Oracle Base edition.

Why does compare not recognize that indexes in different systems are the same but have different names and thus generate a rename command? Instead, it generates a drop index and then a create index which for very large tables may not be feasible?

That would be a nice enhancement. I’ll work on it.

Actually, it looks like we already do that for indexes that are part of a PK or Unique constraint. I just need to extend the functionality to non-unique indexes.

OK, Next beta, non-unique indexes that differ by name will be renamed instead of rebuilt.

John, yes, I should have mentioned it was non primary key indexes… but thanks for including the enhancement.