Skip to main content
Announcements
NEW: Seamless Public Data Sharing with Qlik's New Anonymous Access Capability: TELL ME MORE!
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

QVD creation architecture

I'm looking at setting up a project that would use multiple large source files and I'm wondering what the best way of QVD creation is. Would it be best to have a single QVW that handles all of the source files and creates the QVD files, or have each source have its own QVW to create the QVD?

It seems like having individual QVW files would be practical in case I ever need to make edits, so then I can do partial reloads. However, I'm not sure what the most efficient method and architecture is to create multiple QVD files. Thanks for your help.

1 Reply
Not applicable
Author

Is better for you, create an unique qvw application for extract tables and store them to QVD files in an unique repository (QVD folder). This QVD files, could be reutilize by other qvw aplications.