Vous êtes sur la page 1sur 6

Development Checklist

Data Model Performance

print and laminate for QlikView develope

Design Best Practices

Synthetic keys removed from data model

Use of colors for contrast/focus only

Ambiguous loops removed from data model

Use of neutral and muted colors

Correct granularity of data

Use of templates/themes where available

Use of QVDs where possible

Display optimized for user screen resolutions

Use integers to join tables where possible

Design consistency across tabs

Remove system keys/timestamps from data model

Formatting consistency across objects

Unused fields removed from data model

Most used selections at top - least at bottom

Remove link tables from very large data models

Drop-down selections on all straight/pivot table columns

Remove unneeded snowflaked tables (consolidate)

Developer QV version matches production

Break concatenated dim. fields into distinct fields

Test client types for rendering

All QVD reads optimized

Use of Common Variables for expressions

Use Autonumber to replace large concatenated keys

Use calculation conditions on large charts

Interface Performance

Script Best Practices

Run QlikView Optimizer to test memory usage

Naming standards used for columns, tables, variables

Minimize count distinct functions

Script is well commented - changes date flagged

Minimize nested Ifs

First tab holds information section

Minimize string comparisons

Subject areas each have tab in script

Macros minimized or eliminated

Use of Include files or hidden script for all ODBC connec

Minimize Show Frequency feature

All code blocks with comment sections

Minimize open objects on sheet

All file references using UNC naming

Minimize set analysis against large fact tables

Business names for UI fields

Minimize pivot charts in very large apps

Security script in Inlcude file

Avoid "Show Frequency" feature on large data

Turn Generate Logfile option on

Avoid AGGR function when possible

UPPER() function used on Section Access fields

Avoid IF statements in calculated chart dimensions

Publisher Service Acct added to Section Access

Avoid built-in time functions in GUI (inmonth, etc)

Use numeric flags where possible

Steps to Performance Tuning an Application


Reduce Rows

Eliminate unneeded data volume (rows) from apps (how far back does the app really need to

Reduce Columns

Find unused fields in the data model - use DocumentAnalyzer_V1.5.qvw against your app to
the "DROP FIELD" statements that are generated for the unused fields and place these into a
application, as the VERY LAST tab in the script.

Reduce Distinctness

Reduce distinct values in your application - use the QlikView Optimizer.qvw against your app
that are candidates for these changes. Select the "Symbols" in the Optimizer app to see the
system keys, etc..)

Increase efficiency

Convert fields to numeric that are used in compare expressions, like IF(ClientType = 'Direct'

Reduce data model


complexity

Collapse snowlfaked tables to attain a more pure star schema

Reduce App complexity

Reduce number of tabs/objects in the application, where appropriate

Reduce App complexity

Reduce the number of open charts down to 1 on tabs where this is possible and appropriate

Best Practices

Follow checklist items above in all areas

ew developers

ble columns

variables

gged

DBC connections

elds

ess

ally need to store data?

our app to do this, then copy


these into a new tab in YOUR

st your app to find the fields


p to see these (timestamps,

e = 'Direct'.)

ppropriate

Prefixes
Variables
Key Fields
Flag Fields
Cycle Group
Drilldown Group
Key Field Separator
Temp Fileds/Tables

Starts with a "v"


Starts with a "%"
Starts with a "_"
Starts with a "<"
Starts with a ">"
Separated by "_"
End With "_tmp"

e.g.
e.g.
e.g.
e.g.
e.g.
e.g.
e.g.

vCurrentYear
%CustomerKey
_YTDFlag
<ProductCycle
>GeoDrillDown
Company&'_'&Nbr as Key
Daily_Trans_tmp

e.g.

Customer Nbr instead of CustNo

Field Names
Use business names for fields.
Rename fields in scripts where possible - not in charts and tables

Publisher Naming Standards


Abbr.
All

Abbr. Type
Environment

Meaning
Applicable to all environments

DEV
PRD
TST
APR
JOB
SDF
TSK
DSR

Environment
Environment
Environment
Publisher Item
Publisher Item
Publisher Item
Publisher Item
Publisher Item

Development Environment
Production Environment
Test Environment
Publisher Access Point Resource
Publisher Job
Publisher Source Document Folder Resource
Publisher task
Directory Service Resource

CurrentYear
CustomerKey

ProductCycle
GeoDrillDown
ompany&'_'&Nbr as Key
aily_Trans_tmp

ustomer Nbr instead of CustNo

Vous aimerez peut-être aussi