Toad World® Forums

Big queries


#1

Hi all,

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?

Regards,
Ercan


#2

Hi Ercan,

I’ve tested on table with 10million rows and canceling work fine for me.
Is it reproducible at anytime?

regards,

Alexander


#3

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.


Charles Haines
Senior Software Developer
P: (410) 535-5590 x1196

Recorded Books, LLC
http://www.recorded books.com

On Wed, Jun 23, 2010 at 11:01 AM, S. Ercan Yüzbasioglu
gmail.com > wrote:

Hi all,

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?

Regards,
Ercan

#4

What does it mean “big queries”? A query that runs quickly but then
returns a lot of data to Toad or a query that runs for a long time on the server
before starting to transmit data to the client? It seems that Ercan is talking
about #1 and Charles about #2. Those cases are different.

Igor.


#5

Oh I was definitely talking about #2. I thought the OP was as well, but
perhaps I misread.


Charles Haines
Senior Software Developer
P: (410) 535-5590 x1196

Recorded Books, LLC
http://www.recorded books.com

On Wed, Jun 23, 2010 at 2:38 PM, Igor Manokhin
wrote:

What does it mean “big queries”? A query that runs quickly but then
returns a lot of data to Toad or a query that runs for a long time on the
server before starting to transmit data to the client? It seems that Ercan
is talking about #1 and Charles about #2. Those cases are different.

 

Igor.

#6

I regularly run queries that return millions of rows and have not noticed this
issue at all. Also run queries that run for hours that also seem to work fine
(Although it is very annoying when you cancel them by mistake because you forgot
you had them running :slight_smile: ).

/Mauritz

Quest Software


#7

I agree with Henrik on this one, I can pull 1.5 to 2.0 Million rows, as long as
I have enough system resources.

I am using a Window7-64 Ultimate and Professional systems with 8 gb and 4 gb of
total memory.

It would curious to know what type of system is having this issue and the
resources. …

Hank Freeman

Senior Systems, Database/Data Warehouse Architect

hfreeman@msn. com

678.414.0090 my cell Primary
image002.jpeg


#8

I agree with Henrik on this one, I can pull 1.5 to 2.0 Million rows, as long as
I have enough system resources.

I am using a Window7-64 Ultimate and Professional systems with 8 gb and 4 gb of
total memory.

It would curious to know what type of system is having this issue and the
resources. …

Hank Freeman

Senior Systems, Database/Data Warehouse Architect

hfreeman@msn. com

678.414.0090 my cell Primary
image001.gif