Qlikview 11 hangs when exporting qvd to excel

[#1]

I want to convert a 90MB QVD file into an excel file. This is actually Flight.qvd from the book qlikview 11 for developers. Its not an exercise in the book, but I just wanted to try it. When I convert QVD to table box and then try to convert that to excel, qv11 hangs.

Why does this happen ? Is there any limit on the size you can export ?

My system - Win 7 64 bit with 4GB ram, 7200RPM hdd, Core i5 processor, 200GB free HDD with no programs (except AV) running in background.

I am attaching this file so that you can try it on your system and see if you have the same problem.

[#2]

Okay, luckily I found a workaround. I google qlikview load line by line and just tried this link -

http://www.quickintelligence.co.uk/qlikview-incremental-load/

It was not really what I had in mind, but it gave me a solution. Instead of converting to excel, I tried to convert into csv because that was also causing a hang.

This is how you do it -

[My Table Name]: // If you see directory; then replace directory; with [Table Name]:

code....

more code....

from ....;

//Code to be added for quick conversion -

STORE [My Table Name] into MyTables.csv (txt);

Maybe there is a way to do the same thing for excel ? Qlikview gurus, please advise.

Side note - Qvd is 90mb and csv is about 500mb. Compression factor of 5x !!! Wow !

1,256,076 Rows !!!

[#3]

Hi John Wayne,

I might be mistaken here - correct me if am wrong, but I suspect this due to the fact that there are millions of row in your table and you lack the computing resources to export it. I highly doubt 4GB of ram will do the job. I have faced problems doing so in servers, therefore I suspect it to be a matter of computing capabilities.

Best Regards,

R

[#4]

You probably did not see my answer to my own problem. If the store command can do it almost instantly, then why does right click > export to....fail ?

[jaimeaguilar]

Hi,

I think the problem here is not a QlikView issue, but an Excel issue. Excel cannot handle that number of rows (1,256,075 is not exactly a friendly number for Excel). Talking about the other formats, is not practical nor a good practice to export millions of rows directly from the front-end (that's why it is recommended to use approaches like calculation conditions).

The reason why storing this data to other formats like txt in script take so few time compared to front-end is because script just need to process these rows, not displaying them (like front-end does).

So in conclusion, I know this was just something you wanted to try, however, if you need to export/store millions of rows definitely you need it to do it from script, or use a calculation condition that tell users to select just one year, one month, or any other filter that narrow the number of rows displayed at the same time. I think you would still have troubles exporting millions of rows from front-end even if you had a more powerful computer, and again is not a good practice to do so...

Regards

[Anonymous]

if you want to interrogate qvds a useful tool I use is Q-EYE.

Q-Eye - Overview

[#7]

yes, but export to csv also hung. But script - "store as csv" worked quickly. This seems to be a problem with the tool.