Databases Reference
In-Depth Information
Since the documents in the Presentation Layer will use the transformed QVDs, and
sometimes some base QVDs that required no modification, and will (ideally) read
them "as-is", optimized loads will be ensured at this stage.
QVDs can also be reused with this architecture when the data model of two or more
QlikView documents require the same source data.
This approach is the one we will work from this point onwards
since new transformations will be made to our base QVDs.
A well-designed data architecture, as those presented in this section, can also enable
the possibility of having different QlikView teams working at different stages. For
example, IT developers can prepare the base and transformed QVDs, while business
teams can make use of those to build the end documents without requiring access to
the source database.
Setting up our environment
Now that we've discussed the advantages of using the three-stage architecture,
let's take a moment to set up our Windows folder structure following the
described guidelines.
By copying the files corresponding to this chapter into your QlikView Development
folder, you will have a structure like this:
 
Search WWH ::




Custom Search