Search

Provide complete FTS property values in a DMV/side table by Bob Beauchemin

Closed

4
0
Sign in
to vote
Type: Suggestion
ID: 773212
Opened: 12/1/2012 9:22:20 PM
Access Restriction: Public
0
Workaround(s)
In SQL Server 2012, the ability was added for full-text search to search on PROPERTY values. However, there is no way to retrieve the property value in question. The actual entire property value should be emitted by the parser and available in a DMV or side table. For example:

Suppose I have three documents that have authors of "Bob Beauchemin", "Bob Newhart" and "Bob Gupta". I can do a CONTAINS-based search for documents with authors that have a keyword "Bob", but can't bring back the entire propery value, which would be very useful.

Currently, the closest I can get is using sys.dm_fts_index_keywords_by_property. But think only produces the keywords, not the property values. So, in the case above, I wouldn't know if the actual author name was "Bob Newhart" or "Newhart Bob". And keywords wouldn't include noisewords.

Since this could produce a lot of additional data, perhaps it could be a full-text index option.
Details (expand)

Product Language

English

Category

SQL Engine

Proposed Solution

The actual entire property value should be emitted by the parser and available in a DMV or side table. See description above.

Primary Benefit

Faster Development

Other Benefits

This could improve the usefulness and increase the number of use cases for the full-text search property-based search.

Virtualization

 
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 4/23/2013 at 7:18 PM
Dear Bob,

Thank you for submitting this feedback. Having better insight into the matches would indeed be very useful. However, after carefully evaluating all of the suggestion items in our pipeline, we are closing this request since we will not implement in the near future due to current higher priority items. We will re-evaluate the closed suggestion again in the future based on the product roadmap and your continued feedback.

Thanks again for providing the product suggestion and continued support for our product.
Michael
Sign in to post a workaround.