Generally, WBs will parse the '&' character as a separator and therefore emit the terms on both sides of this character. We already posted on this blog how to avoid this default behavior by using custom dictionaries. Note the following though, SQL Server Full-Text Search Parser will see this character...