Qlik Community

QlikView App Dev

Discussion Board for collaboration related to QlikView App Development.

Announcements
Customer & Partners, DEC. 9, 11 AM ET: Qlik Product & Strategy Roadmap Session: Data Analytics REGISTER NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
prachi91
Creator III
Creator III

ETL layer in qlikview

How to develop and design ETL layer in qlikview?

thank you..

5 Replies
vamsee
Specialist
Specialist

Hi Prachi,

Can you please elaborate your question.

ETL: -- Create 3 Apps

Extracting Data all your data with most basic filters.

Transforming your data according to a specific app or joining and creating qvd's.

Loading all your Qvd's into the final app with minor changes or joins, charts.

Digvijay_Singh

There are many topics here in community on this. You will find similar diagram as below explaining end to end process of Qlik Data Architecture development. In my opinion Qlikview 11 for developers book is the best resource to start with.

Capture.PNG

qlikviewnovice
Specialist II
Specialist II

Hi

Community.jpg

Advantages of III Tier Architecture

1. Reduces the load on databases/sources.

2. Load time of Dashboards is reduced because of the reduction in the source hits.

3. Data is consistent across all the Dashboards.

4. We can split the development process and assign it to multiple developers.

5. Very secure method, even we distribute the Qlikview file users cannot be able to find the source,

transformation details.

Disadvantages of III Tier Architecture

1. It takes bit extra time to develop.

2. Need to create more tasks in Publisher for reloading.

Siva_Sankar
Master II
Master II

Looks like you are preparing for some interview..all your questions in the community said it. You can better to learn from the learning materails and practice it then you ask questions.

SDLC in qlikview

compare Qlikview and Qliksense

Genric load In qlikview

ETL layer in qlikview

Preceding Load & Resident Load

Also, even after getting the answer you didnt mark any answers as correct for our fellow community contributors. Not good.

-Siva