I am so sorry,I asked my question in a wrong way.Yes I know that we have problem in one of our queries,and I am involved.(The logical io is too high(3939737 for 43300 record) and after update statistics the estimated number of rows is still 1.Total number of extents for that table is 1284925.)

So because of this problem we have time out in insert statement.I want to know if there is a way to kill these queries until I find the solution for the query performance.

At the moment developers set the app's timeout to 40 seconds,but the query is still running after it shows timeout error to the users.