Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I've been looking at the MetaData at the start of some of my QVD's (with the excellent QViewer). This shows the connection details and query used to bring in the data for any given QVD.
I have one particular QVD Generator that enumerates around quite a number of databases and writes a number of QVD's out from each of them.
As the routine goes on more and more data is written to the metadata of each QVD - showing all statements and connections prior to that QVD being written. This is a massive amount of bloat and completely misleading information.
Is there a way in which the cache of meta data that is written to each QVD can be flushed? My assumption would be that this should happen automatically - but in this case it is not. This ability to flush meta data would also be useful when people get nervous about connection strings appearing in QVD's.
I am running in QlikView 10 SR 4 (10.00.9282.8), and unfortunately can't install a fresher version into the environment where I am seeing this issue.
Thanks in advance,
Steve
Hi Steve,
I have seen this before with data lineage information causing problems. Have you seen this post:
http://community.qlik.com/message/183575#183575
So, just set the AllowDataLineage to -1.
Not sure if this works on server - but if it does then it will be in C:\ProgramData\QlikTech\QlikViewServer\Settings.ini - add an entry for AllowDataLineage=-1 to the [Setting 7] section.
Stephen
Hi Steve,
I have seen this before with data lineage information causing problems. Have you seen this post:
http://community.qlik.com/message/183575#183575
So, just set the AllowDataLineage to -1.
Not sure if this works on server - but if it does then it will be in C:\ProgramData\QlikTech\QlikViewServer\Settings.ini - add an entry for AllowDataLineage=-1 to the [Setting 7] section.
Stephen
Although that doesn't quite make sense as it would be the distribution service doing the reload, not the server service.
Worth trying though!
Stephen
Thanks Stephen - that has pointed me in the correct direction. This thread is also worth a look: http://community.qlik.com/thread/49240
It seems that getting my client to upgrade to the latest and best version may solve the issue also.
Cheers,
Steve