cancel
Showing results for 
Search instead for 
Did you mean: 

Fuzzy search index on NVARCHAR

former_member185171
Participant
0 Kudos

Hello all,

In order to be able to do a text search on a column it has to be declared as a TEXT column. Up to now we have HANA as a secondary database, and apparently all "text-like" columns are translated during replication into type NVARCHAR.

For the text search we then have to declare a fuzzy search index on these columns. This enables this kind of search:

SELECT SCORE() AS score, id, s

FROM text_spell_check_factor

WHERe CONTAINS(s, 'Müller', FUZZY(0.5, 'spellCheckFactor=0.9,textSearch=compare'))

ORDER BY score DESC;

In our intake system we have converted our database to HANA (as primary) and I notice that all "text-like" columns are also defined as a NVARCHAR.

Is this the normal way of working? Because the we will also have to define this fuzzy search index on our primary database. This should be automatically done if the conversion translated the columns differently (to TEXT e.g.).

Thanks for any reaction.

Regards.

Kris

Accepted Solutions (0)

Answers (1)

Answers (1)

lbreddemann
Active Contributor
0 Kudos

What replication technology are you using?

former_member185171
Participant
0 Kudos

Hi,

we are using SLT for the replication to the secondary database.

lbreddemann
Active Contributor
0 Kudos

Ok, then the reason is quite clear. SLT can only support data types as they are available from the client point of view.

HANA TEXT data types appear to the client like large NCLOBS.

For all practical matters I wouldn't know how to replicate those TEXT types between two SAP HANA instances.