What Gail says.
But, just a little bit of help without the details.
All those != commands are going to prevent good cardinality estimates from the optimizer which is likely to lead to a poor plan. OR statements are frequently better served by using a UNION ALL command to do the two sides of the OR.
I can't say much more without at least the execution plan as a guide.
"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