Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi All
PLease find the aatachment of the screenshot of the script loading ,
as u can see the time elapsed is more than 1 hour and its still loading ,
at 21875 it fecthed in 1 second but after that its not moving forward.
Can some one suggest me what needs to be done , the data is coming from oracle data base which has around 1 lakks rows .
and there are some calculation involved in the sript .
Thanks in advance...
What's huge and what's the script?
Hi Gysbert
When i say huge its the data , there are around 1 lakh rows and the script has calculation too,
Hi John,
1lakh is not a big deal for the Qlikview, I think you have issue with the SQL joins and condition please check the SQL connection and conditions once .
Hi john I understand your problem, All this issues comes if the SQL Conditions and connections are not correct in that case only the script keep on executing like that....
Hi John
I suggest, store the data in QVD and then load into your new QVW (through binary load)... essentially 3 tier architecture.
Regards,
Sreeni
More than 1 hour is definitely very slow for ~23000 rows. Be aware of the fact that QlikView sometimes update the log window in bursts. Especially if the SQL query is chewing on the SQL logic using complicated joins and has to do a lot of internal (seen from the SQL DB engine) operations while or before it can deliver rows makes this especially true - long time without any updates. The lack of indexes in your SQL database that should support the SQL query being executed can lead to extremely low performance and little can be done from QlikView to fix this.
The number of columns is a significant factor in speed. It is all a matter of maths
x columns * y rows * size of each column data type = total data volume
Picking out only the number of rows as a measure for the volume that needs to be loaded is too one dimensional really.
The other significant factor is of course how fast your source database can deliver the rows. This again is also dependent on both the complexity of the underlying SQL query and of the performance of the SQL engine.
Thanks for the detailed information Peter ,