Sort Index Normal

[Former Member]

Turning on Sort Index before Importing the data is it a Good Practise?, Does it make the Import a Lot Slower, On Average for a main Table of 200 fields what should be the critical Number for Sort Index fields count before the system starts to break down?

Ideally shouldn't the Indices be updated only when we Load the server "Update Indices" way and not affect an Import?

-Sudhir

[Former Member · Accepted solution]

Hi Sudhir,

Sort Index property on the Fields in the MDM repository in to make those Fields as sortable in the MDM Data Manger and the API,

That is the fields set as sortable in MDM Data manager can have their Field values either sorted in Ascending or Descending order but however MDM spends extra memory and processing to maintain the sort index, which can dramatically slow down updates and imports on larger repositories. To improve system performance u2013 or if you donu2019t think you will need to sort on a particular field u2013 do not make it sortable.

Turning off sort-indexing for fields in Lookup [Flat] tables can improve MDM performance, especially when loading a repository while some fields always have their sortable propert set to none.

MDM sorting thus is an useful feature but must be used wisely as it adds overhead.So restrict the Sort Index propert in the following cases:

- When you have fields whose values needs to be arranged in an order mostly alphabetical order for text fields such as material desciprition or type.

- It accelerates free-form search for the equals and starts with Text operators,so for fields that need free form search on them can have this prperty set.

- It also improves the Matching speed in the MDM Data manager,So can be set when data deduplicaion are performed.

Hope It Helped,

Thanks & Regards

Simona Pinto

[Former Member]

For now I am assuming Sort Index is like Query performance tuning and should be turned-on on a need basis after entire data Load.

Thanks for your replies