2016 what are the three ways and efficiency problems of fuzzy matching?

Today, I will talk to you about the three ways and efficiency of 2016 fuzzy matching, which may not be well understood by many people. in order to make you understand better, the editor has summarized the following contents for you. I hope you can get something from this article.

An example is given to describe the three ways and efficiency of SqlServer2016 fuzzy matching. The details are as follows:

The database is Sqlserver version 2016

Now the business requirements are: to query the following enterprise names, XXX,XXXX, and so on:

The first way: like'% XXX%' OR like'% XXXX%'

Select cName from tAccountAuditing wherecNamelike'% Test moa000154%'ORcNamelike'% Shanghai Division of Test Group% 'and activeAuditingCodeFromJdjr = 1

The second method: PATINDEX ('% XXX%',cName) > 0

Select cName from tAccountAuditing where (PATINDEX ('% Test moa000154%',cName) > 0ORPATINDEX ('% Test Group Shanghai Division%', cName) > 0) and activeAuditingCodeFromJdjr = 1

The third way: CHATINDEX ('XXX',cName) > 0. Don't use the percent sign here.

Select cName from tAccountAuditing where (CHARINDEX ('Test moa000154',cName) > 0ORCHARINDEX (' Test Group Shanghai Division', cName) > 0) and activeAuditingCodeFromJdjr = 1

In terms of efficiency, the latter two are better than like.

After reading the above, do you have any further understanding of the three ways and efficiency of 2016 fuzzy matching? If you want to know more knowledge or related content, please follow the industry information channel, thank you for your support.