Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi All...
We are in the midst of upgrading from version 8.2 to 9.
In the process, we are also moving on to a different server which has slower processors but more memory (moving from 4gb to 32gb).
I update my QVD tables via batch files / windows scheduler.
Ran a side by side test pciking a specific point in my update file.
Old server took 15 minutes, new server took 23 minutes to reach this point.
We cannot unfortunately transfer the memory between servers as it is not compatible.
The current thought is that we just buy more memory for the old server but want to avoid spending if possible.
Before we head down this road, are there any settings in QlikView 9 / the server (Windows 2003) that we can tweak to try and improve performance?
Any help greatly appreciated....
Hi,
There are ways to improve the performance of the load script by making it consume more memory, but be efficient in terms of CPU usage.
Cannot help much without looking at the load script.
Thanks Vidyut...
The attached word document shows the detail behind my Customer QVD table...
This is one of many scripts that I have...
Paul,
Not really related to your original question but I think you should reconsider the need for the joins....
You dont need to append the descriptions to your main tables such as:
LEFT JOIN (TempCustomer01)
LOAD
Code AS cus_ARType,
"Code-Desc" AS cus_ARTypeDescription;
SQL SELECT
Code,
"Code-Desc"
FROM PUB."cde_codes"
WHERE Prefix = 'FAR-CT';
- just let Qlikview do its associative thing ie remove the 'LEFT JOIN (TempCustomer01)'. This should speed things up a bit, especially if the join tables are large.
Regards,
Gordon
Thanks Gordon
The aim of this script is to produce a single QVD customer table which includes the description of the respective code from our codes table (example above is adding our ARType description). This QVD table is then used in other reports along with other tables such as SalesInvoice.
If I don't left join, when I do the store, the description fields are not included in the QVD table output.
When we are doing the reports, we let QlikView do its thing by letting it join based on the keys which we have defined as you have suggested.
Thanks for the suggestion, appreciate the difficulty in providing advice when you are only seeing a snippet of the information...
Best Regards
Paul