This produces extremely bad SQL which will have a dreadful performance.

Calling a table with 5500 rows a large search is a laugh, my customer table has 3.6 million rows in it....

A far better way would be to build a query @string variable suitable to meet the exact query and exec(@string) instead.