I’ve had this problem before as well. I’ve actually had to kill TOAD
through Windows and then kill the process in SQL Server. Usually I can cancel
it quickly, but it appears that if I have left the query running for a while
before cancelling is when I run it to issues. I also notice if I’m dumping
into temporary tables I can get this problem as well.
Senior Software Developer
P: (410) 535-5590 x1196
Recorded Books, LLC
On Wed, Jun 23, 2010 at 11:01 AM, S. Ercan Yüzbasioglu
gmail.com > wrote:
When I accidentally run a query that returns a very big result set, no
matter how hard I hit the cancel button, I cannot stop it after 5~6 secs. I
don't know if that is Toad's fault or SQL Server's, but I find
it very annoying. Does it happen to you too or am I the only one?