5/20/2023 0 Comments Qvr client failed to connectI have personally seen several server jobs fail because qvconnect.exe decided to eat all of 10GiB of memory! I am not sure why the process refuses to relinquish its memory, perhaps it is trying to cache some of the dimension values for later use. The reason for this is that it appears that qvconnect.exe/ qvconnect64.exe does not garbage-collect between loops (or indeed PseudoMDX statements) so as a result, its memory footprint will steadily increase until your loop/script finishes or your machine runs out of memory. How can I avoid this happening without using separate documents with separate scripts? However, I have found that if you are running a large number of loops, even though you are not returning many rows in each, QlikView will often stop loading with an "out-of-memory" message. Now, this works for relatively small result sets as the memory requirement is within reasonable limits (I monitor the QlikView connector qvconnect.exe/ qvconnect64.exe - 64-bit). LET MonthValue = date(addmonths(StartDate, $(Month) - 1),'YYYYMM') ![]() Rather than have endless repeats of the same SAP Connector Script that changes only by the month and year parameters, I decided to put them inside of a for-next loop as follows: CUSTOM CONNECT TO "Provider=QvSAPOLAPConnector.dll MSHOST=server1 R3NAME=SBW GROUP= CLIENT=100 Log=1 XUserId=ABCDEFG XPassword=ABCDEFG " ![]() ![]() I often have to extract months and months of data from SAP Business Warehouse (BW) in one go in QlikView and to do this I use QlikView’s own SAP OLAP Connector.
0 Comments
Leave a Reply. |