Data Extraction 

To manage data extraction and transformation, QlikView has an extensive ETL layer. Using SQL to connect to underlying data sources, QlikView allows users to quickly connect to their data.

In Memory

Because QlikView operates entirely in memory it does not require data to be stored in specific, aggregated, proprietary formats such as cubes. This reduces implementation costs significantly.

Associative

In addition, QlikView automatically detects and manages the associations between your data tables. Thus, loading data into QlikView is as simple as loading individual tables and letting QlikView associate the data.

Data Compression

Because we work in memory, QlikView compresses data as it is brought into memory. QlikView automatically reduces redundancy in data, and maps all data to memory-based pointers to minimize the memory footprint of QlikView analysis. The result is that data is typically reduced 10x (10:1 compression) from typical relational stores.

QlikView Server

The QlikView server is used to organise automated reloads and user mangement. All deployment options – AJAX, plug-in, full client, PDF and mobile – are all managed from one central location.
QlikView’s application and deployment options enable you to deliver the right functionality through the right medium to each user group.

Deployment

QlikView’s application and deployment options enable you to deliver the right functionality through the right medium to each user group.
QlikView provides:

• Extensive APIs that enable QlikView functionality to be integrated with your business applications
• A zero-install AJAX client that gives end users a full analysis client with no local installation hassles
• Mobile accessibility, including iPhone, BlackBerry and Symbian clients, that give your team an integrated way to deliver QlikView to mobile users
• Virtualized environments that fully utilize existing hardware and cloud deployments to maximize flexibility in deployment architecture