the QlikView application file, .QVW, contains the presentation layer (charts, tables, etc.), the script and all the data.
Usually, the data is the heaviest part.
If you want to shrink its size, you have several solutions like:
- Change the model to reduce the numer of columns, distinct values (unique keys and Link Tables are expensive)
- Change the compression level of the file: User Preferences > Preffered Save Format
- Remove the data: File > Reduce Data > Remove all values
But if you are in an Entreprise environnement, you probably have a QlikView Server.
You can add a variable which is tested at the beggining or your script and exits the script when set to 1, in order to have no data, like
If vExitScript = 1 Then
Then, in the server configuration, you could have a task loading the data with parameter vExitScript = 0, and another one loading the data with parameter vExitScript = 1, resulting in an application without data and that you could backup.
yes, we have a QlikView server, but as up to now we do our Backups ourselves - we don't have a tested and proven Backup-routine in place yet, so we'd rather trust ourselves - so that menu-point
>>> "Reduce data->Remove all values"
should do just fine.
I will try it out.
Thanks a lot!
P.S.: Yep - that reduces the size of the file to backup by about half. Perfect!
You could use (extern) versioning-tools which could directly included in qv. But the handling won't be very easy in the beginning and it will cause additionally cost.
To copy all important apps is always a good idea. To save hd-space you could reduce the amount of data within the app, emptying isn't the best way because some data-structures could be destroyd (variables). I don't know if this could be done automatically.
Another possibility could be to read/export all data- and objects-structure in txt- and xml-files and restore apps on demand.