EMAIL_OPTIMISED Match
Same matching behavior as EMAIL with faster evaluation on large datasets. The production-scale choice for email address matching in Enterprise.
What EMAIL_OPTIMISED does
EMAIL_OPTIMISED produces the same matching results as EMAIL - it splits on @, discards the domain, and scores the local part using the similarity function. It is not an exact/binary comparison; it is FUZZY.
The scoring pattern is exactly the same as EMAIL - only the computation time differs. EMAIL_OPTIMISED is substantially faster when comparing large numbers of email addresses.
What EMAIL_OPTIMISED matches and what it does not
Partial - same as EMAIL, local parts differ but share "smith"; scores a graded similarity, not a hard match or non-match
Yes - identical local part, even though the organisations are unrelated
[null]
Yes - same as EMAIL, a null/blank value on either side is an automatic match; add NULL_OR_BLANK if you want nulls excluded
When to use EMAIL_OPTIMISED
When not to use EMAIL_OPTIMISED
Last updated
Was this helpful?