
Page 10
In Step 2/2, check the Updateable Cursors checkbox to enable the ODBC driver to use cursors.
Tuning QlikView and Redshift for performance
For performance reasons, it is recommended that complex SQL queries (such as multiple sub-selects and complex
joins) are not executed from QlikView. A Best Practice would be to perform these types of queries within Redshift
and send the resulting data set to QlikView via extraction through ODBC or Direct Discovery.
Below are some reference documents on how to design an Amazon Redshift Data Warehouse to work well with
Qlikview.
•
Design Tables for fast read
o
Be able to understand and analyze explain plans
Link http://docs.aws.amazon.com/redshift/latest/dg/c-optimizing-query-
performance.html
o
Selection of correct sort keys
Link-http://docs.aws.amazon.com/redshift/latest/dg/c_best-practices-sort-key.html
o
Selection of best distribution keys
Link-http://docs.aws.amazon.com/redshift/latest/dg/c_best-practices-best-dist-
key.html
o
Smallest column size and data set.
Link - http://docs.aws.amazon.com/redshift/latest/dg/c_best-practices-smallest-
column-size.html
o
Compression
Linkhttp://docs.aws.amazon.com/redshift/latest/dg/t_Compressing_data_on_disk.ht
ml
o
Be able to understand data distribution
Link http://docs.aws.amazon.com/redshift/latest/dg/t_Distributing_data.html
Kommentare zu diesen Handbüchern