Toad World® Forums

Quick Export failure [1 Attachment]


#1

[ Attachment(s) from Tad Groves included below]

What is the limit when exporting results to an Excel instance? I have a result
set containing 65810 records.


#2

It depends on which version of Excel you have installed. If you have Excel 2003,
the limit is 65536. For 2007 and later it’s over 1 million. Did the export
overflow to another worksheet after you hit 65535 (assuming you’re
exporting to a 2003 Excel instance)?

Alan


#3

The error in the exception log shows that an error was thrown when showing the
Summary window. The export should have finished successfully at that point. Are
all the rows there?

Also, on that many rows you might want to consider CSV as it is more efficient
than exporting to Excel.

Debbie


#4

I’m using Excel 2007 and there were no records on the second or third tab.


#5

Alan and Tad,

I work on the Toad-SS product as a user and I have successfully imported over
300K rows and I believe that you need a big honking system like my desktop of
8gb and Windows 7-64 to not have issues. Recently, It was a reported that
Toad-SS had row count issue, which I have not been able to reproduce, but that
issue should be in the knowledge base.

As a rule of thumb I always do a select count or use another utility I wrote to
make sure of the row count before I import into excel.

Lastly, a QA person here was performing an import via SSMS and she dropped over
100k rows in the cut and paste process so the word here is know how many rows
you need to import and check the count in excel taking nothing for granted.

Hank Freeman

Senior Systems, Database/Data Warehouse Architect

hfreeman@msn.com

678.414.0090 my cell Primary
image002.jpeg


#6

Alan and Tad,

I work on the Toad-SS product as a user and I have successfully imported over
300K rows and I believe that you need a big honking system like my desktop of
8gb and Windows 7-64 to not have issues. Recently, It was a reported that
Toad-SS had row count issue, which I have not been able to reproduce, but that
issue should be in the knowledge base.

As a rule of thumb I always do a select count or use another utility I wrote to
make sure of the row count before I import into excel.

Lastly, a QA person here was performing an import via SSMS and she dropped over
100k rows in the cut and paste process so the word here is know how many rows
you need to import and check the count in excel taking nothing for granted.

Hank Freeman

Senior Systems, Database/Data Warehouse Architect

hfreeman@msn.com

678.414.0090 my cell Primary
image001.gif


#7

I just exported 70,000 rows to an excel instance and all exported to the first
sheet. I am using Excel 2007. Can you try and again and post a screenshot of the
error?

Debbie


#8

[ Attachment(s) from Tad Groves included below]

Here’s the screen shot and the support bundle from 8/31.
image001.png


#9

I looked at the code today. We actually do a system resource and memory check every 100 rows. If this function found the resources low you would have been asked if you wanted to continue. Therefore the issue could be something else. More details on the execption are written to the Error log. Did you get the finished window? You need to press the error log hyper link and look at the log. Can you do this and send to us?

Debbie


#10

Was that in the support file I sent?


#11

No. The logging is not written to a file but is in memory so is only show in the Error log review window.