Export to excel_urgent

[#1]

Hello Community,

I have 20 million rows in a straight table. When I export to excel my QVW file stops responding.

Also the performance and response time is not user friendly. The tool size is 436 MB and I, now, have to add this straight table.

I know Excel cannot handle so much data. Can anyone give me a way about this?

Also, Can anyone suggest me a checklist so that I could improve the performance. Exporting to excel is high priority for me. Please reply asap...

Thanks,

Vishal

[javier_florian]

You can create a store...

STORE Table_Name INTO file_name.qvd (qvd)

STORE Table_Name INTO file_name.txt (txt)

[#3]

Hey Javier,

Can you explain a little further please?

I had a Data base and converted them into QVD. Now, I am using the QVD's to populate my straight table... The straight table has 20 million rows in QlikView front end... So I don't know a way around this.

Kindly reply

Regards,

Vishal

[javier_florian]

Hi Vishal,

Do you need export >20M rows, you server will shut down... so, if you used a STORE to export data, your performance doesn't decrease... let me know if it work for you

[#5]

Hey Javier,

Thanks for your time! I have one question.

In the script,

STORE Table_Name INTO file_name.txt (txt)

What would be the table name? Do you mean the table ID??? and can it be stored as csv???

I am sorry. I am a newbie

[javier_florian · Accepted solution]

For example:

ODBC ....

Table_1:

SELECT ...

FROM ...;

Table_2:

SELECT...

FROM ...;

STORE Table_1 INTO my_file.csv (csv)

STORE Table_2 INTO other_file_name.csv (csv)

[#7]

thank you Javier

[#8]

In my understanding if you are using a straight table to show your information, no calculations are made so you can fit your model in order to create using "join" or "mapping" or "lookup" a joined table in qlikview memory and then throw store statement to store it in CSV.   If you provide us with your data model I could be more specific.

[javier_florian]

If you work with big data, performance could decrease on your server... In straight table, you can export data directly, but it can impact your performance

[#10]

I didn't comment performance aspect. This is the reason because I said to make export in qlikview script instead of in an object.  In script performance issues could be solved easier.