全文搜索号码在SQL Server 2012中不起作用

Question

Fulltext search numbers does not work in SQL Server 2012.

I tried to create an empty_stoplist and repopulate the index. Can anyone tell me what I am doing wrong here?

CREATE FULLTEXT CATALOG Orders_FTS
WITH ACCENT_SENSITIVITY = OFF;
GO

CREATE FULLTEXT INDEX ON dbo.Orders
( 
     a Language 1031,
     b Language 1031,
     c Language 1031,
     d Language 1031
) 
KEY INDEX [PK_Orders]
ON Orders_FTS; 
GO

CREATE FULLTEXT STOPLIST EMPTY_STOPLIST;
ALTER FULLTEXT STOPLIST empty_stoplist DROP ALL;
ALTER FULLTEXT INDEX ON Orders SET STOPLIST EMPTY_STOPLIST;
ALTER FULLTEXT INDEX ON Orders SET STOPLIST = OFF;
ALTER FULLTEXT INDEX ON Orders START UPDATE POPULATION;

The SQL query:

SELECT
    T.*, R.RANK 
FROM  
    Orders As T 
INNER JOIN  
    CONTAINSTABLE(Orders, *, '"*007440147*"') AS R  On T.ID = R.[KEY]  
ORDER BY 
    RANK DESC, ID DESC

Answer 1

The problem is that leading wildcards (ex: *bcde ) are not supported by SQL Server. (More here .) The query will execute without any errors but will always return 0 results. You can only use wildcards in the middle of a string (ex: ab*de ) or the end of a string (ex: abcd* ).

Usually this can be worked around by creating columns that contain the reverse string and searching on those columns (ex: Column1 = abcde , Column1Reverse = edcba , query has CONTAINS(Column1Reverse, '"edcb*"') ).

However in your case you want to use a wildcard at the beginning and end of the string. I think your options are limited to:

1. If you don't need a leading wildcard, then don't use it. For example, if the text you are trying to match is 007440147xxx then using 007440147* in your query will work fine.
2. Use LIKE instead of CONTAINSTABLE , for example: SELECT * FROM Orders WHERE Column1 LIKE '%007440147%' . The downside to this approach is that you won't get a rank value and queries may take a long time to execute. (Then again, even if you could use a leading wildcard in full text searches, they would be slow.)
3. Redesign how the data is stored and queried. I can't offer any suggestions without understanding what these numbers mean and how they need to be queried.
4. Consider using another search product. I believe Lucene can perform leading wildcard searches but such searches tend to be slow.