Coalesce field not indexed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-15-2017 02:22 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-15-2017 02:26 AM
Hi Johnny,
It best practice to index any field you are using to coalesce on. It will improve the performance of your transform process no end.
Nice post on it here: Improve Import Set performance with the coalesce index feature in Fuji
Regards,
Paul.
Regards
Paul
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-15-2017 02:58 AM
Hello Curwen,
Thanks for the reply! I have gone through most of the posts which in the community which include the coalesce index issue. i undertsand that this is the best practice we should follow. For some reason, we are not allowed to create a new index field. This is the reason I posted this to know if there is any impact on target table if we continue to use the coalesce field which is not indexed.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-15-2017 05:55 AM
If you continue to use the coalesce field without an index, your imports will be impacted, but not the target table.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-15-2017 06:32 AM
thank you Mr.Tomasi.. That is what I wanted to confirm!