The information in this article applies to:
SYMPTOMSWhen performing a full-text search on SQL Server character data, or when using a SQL distributed query with the Microsoft Index Server OLE DB provider (MSDIXS) and a prefix expansion search for a compound word that contains a hyphen (for example, "XYZ-A*"), the results produced may not be as expected. CAUSE
A full-text search considers a word to be a string of characters without spaces or punctuation. The occurrence of a non-alphanumeric character can "break" a word during a search. Because the SQL Server full-text search is a word-based engine, punctuation generally is not considered and is ignored when searching the index. Therefore, a CONTAINS clause like 'CONTAINS(testing, "computer failure")' would match a row with the value,
"The failure to find my computer would be expensive.".
WORKAROUNDTo work around this problem, try the following:
STATUSThis behavior is by design. MORE INFORMATION
Microsoft SQL Server version 7.0 provides the ability to perform a full-text query on character data stored in SQL Server tables. You can also use a SQL distributed query with the MSDIXS provider to search for file system data. Using the dash ('-') in a proximity search is not supported and may give unexpected results. REFERENCES
For more details on SQL Server 7.0 full-text search, refer to the SQL Server 7.0 Books Online.
Q182829 DOCERR: Prefix Expansion with Index Server OLEDB Provider 2.0 Textual Searches on Database Data Using Microsoft SQL Server 7.0 Additional query words: kbDSupport oledb filesystem alpha numeric alpha-numeric
Keywords : kbDatabase kbOLEDB kbSQLServ kbVC |
Last Reviewed: August 31, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |