In your results, do you care why the row was selected? If you need to know if the row met the "='333777'" clause or the "!='33777'" clause, you're going to have to add another column to your result set so you can tell them apart.

And even then, I'm not sure it's possible from a quick look at what you're trying to do. Well, you can just do a trivial "(long query1) UNION (long query2)". But that won't be any faster than what you're running now, and might in fact be slower because you might have to spend time pulling the results apart into the two separate sets that you're getting with two queries.

But if you do figure out a way to combine the queries, is it worth it? They're already complex enough that you need help to combine them. What happens after you combine them and find you need to modify them?

Why do you think you need to do this? Is it using CPU cycles and time on the database server? Well, that's why that database server was bought in the first place. If you're not using all the CPU cycles on it your company wasted money.

This seems like a bad idea to me from what you've posted. It's already very complex, but it works now. Making it more complex in ways you don't understand is going to help how? What happens if the more complex query breaks?

Just because you write code on your job doesn't mean every problem is best solved by writing more code.