• I'm with Joe and Dwain.

    You do have an option, but it's somewhat dangerous. SQL Server has a function called SOUNDEX that sounds out how a word would be spoken. This allows you to take two words, spelled differently that do mean the same thing and possibly get them to link together. However, it's a very inaccurate way to go about it. And, putting the function on the column would prevent index use. You could store a soundex value in a column and then compare parameters to that. But you're still going to hit the accuracy issue.

    Go with Joe & Dwain's initial suggestion.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning