Perhaps a rather incomplete example will help:
SET @sqlquery = ' SELECT * FROM TestMyView WHERE 1 = 1 ' +
CASE WHEN @sexID <> 0 THEN ' AND sexID = @sexID' ELSE '' END +
<More CASE statements - one for each part of the WHERE clause
-- Then call sp to execute
EXEC sp_executesql @sqlquery, N'@statusID=@statusID, @sexID=@sexID' -- one for each of your filters
,@sexID=@sexID
,@statusid=@statusid
Note how I include WHERE with 1=1 so that subsequent concatenates to the string can be started with AND.
My thought question: Have you ever been told that your query runs too fast?
My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.
Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St