Custom proximity search is a new feature introduced in SQL Server 2012 Full-Text Search. It's facilitated using the NEAR operator, allowing it to be used in the CONTAINS predicate or CONTAINSTABLE ...

where @searchPhraseis currently an NVARCHAR(1000) and holds the result of a function call that puts together the full search phrase. This all works fine as is but a long search string will increase ...

Just wondering if anyone has had to do this and what you thought the best way was?<BR><BR>It's for a customer services type program so it's holding the standard sort of data you'd have on people.