This content has been marked as final. Show 3 replies
I understand the difference between optimized vs non optimized loads, and clearly an optimized load is preferred. However, due to business requirements, data transformations in the script (such as filtering data sets, creating new calculated fields, concatenating fields for keys...etc) are inevitable. All of these transformations (except the filtering data sets using WHERE exists) force a non optimized load.
Is it possible to (for example) create a calculated field while maintaining an optimized load?
You may say that I should perform the calculations on the database side, store already transformed data into a QVD and then optimize load into a QVW. However, to maintain flexibility, I chose to perform the transformations at the QlikView level.
Any tips and tricks are appreciated.