Need Help with Triggers

I am not actually sure if Triggers are the solution to my problem, but I have no experience with them and need help understanding if they will solve my problem.

Users that Access the database through our Front End Software can search on any field (indexed or not). For the most part, they search on indexed fields, but the problem is when they enter and empty string and attempt a search.

The Query that is passed to SQL essentially searches for everything - example below:

SELECT FieldA, FieldB, FieldC FROM Table WHERE IndexedField LIKE ''%'' ORDER BY IndexedField

The result of this is a timeout after 60 seconds and the server being practically coming to a halt during that wait. All users trying to make reads or writes are queued behind that query and it appears as though they are frozen. I have done a lot of monitoring with Profiler to figure out the problem, but I am stuck on how to stop it. The issue lies with the users and that is something I cannot fix. The Front End software cannot be modified. I cannot limit what they search on nor can I limit the fields they can search on.

Being that I can't do anything there, I was hoping I could intercept this query when SQL receives and possibly time it out faster. The queries follow a format, so I was hoping a trigger would do the trick.

Please provide any ideas or input that may help solve my problem. Also, if anybody has any good links to help me with triggers if that will take care of the problem.

EDIT: After doing some reading it is looking like triggers may not be applicable to my problem, but I am still looking for a solution.

Thanks in advance,

Don

But there is no select trigger.

I understand that, I edited my post after I realized triggers weren't the answers, but I am still hoping that there is something I can do to intercept specific queries received by the server.

You should do it in front end.