History Data: How Do You Handle It?

[#1]

Hi,

In the last few years we took historic data out of our main applications in order to maintain a good response time.

We created copies of our main applications and left them as is.

Today this practice is giving us a headache. Mainly in terms of security because users are removed and added but the applications Section ACCESS is not updated. Now we've archived the source data in our main database so we would need to restore this data in order to refresh the QlikView applications. This is of course a lot of work and also a problem due to available disk space on our system.

I am curious to know what everyone take on this was. Surely we are not the only customers who need to put aside history data.

I have try the Partial Reload in order to reload only the Section Access but I get General Script Error. I have browse through the forums and it seems that the Partial Reload is not able to modify the ACCESS data. Has anyone been able to accomplish this?

[#2]

I think that it could be a good idea handle Access section through an include file, as it was a configuration. Then, all your copies could point to the same file and share the same access section that you maintain up to date.

To archive data, I was working using partitioned QVD files by date (1 file per month) using a standard naming convention (e.g. Transactions_200901.qvd). Then, I use the ability of QlikView to Load files using wildcards 'Transactions*.qvd'. I have a set of support functions (SUBs) in a couple of .inc files that I include.

[#3 · Accepted solution]

Ok so we figured how we were going to handle this.

We created a new application to binary load our archived application then stored tables to QVDs using STORE. We then created a copy of the application, erased the script except for the ACCESS section and loaded all of the original tables from the QVDs generated on the first step. The reload only takes a few minutes and the security is updated.

For those who don't know, the Binary instruction lets you load all of the data (without variables) from another QVW. Look in the help for more details, it needs to be the first line of the script or QV will give an error.