Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us to spark ideas for how to put the latest capabilities into action. Register here!
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Handling a model having 1500 Millions records for 2 years. What would be best design of App?

Hi All,

I have an application which holds 1500 millions or records. One of its Dimension is Touch Type, which is having only 2 values Touch On and Touch Off.

So when Employees are coming to Office They will touch there card and that will count as 1 Touch On. If they go Out of Office again they will touch there card and that will count as Touch Off.

So for each card will having individual touch on and off counts. I have 2 separate Facts Fact_Touch_On_Count and Fact_Touch_Off_Counts

and these 2 I am concatenating in my application.

Generally Users will seeing count of touch on and off based on date dimension as well as Touch Type.

As of Now I am concatenating both the facts data into 1 in my application.

During training, we have being taught that If we have small dimensions, It is better to merge then in fact and also try to keep only one fact table by merging then because that gives better performance in qlikview.  I have done this but still not much improvement.

Now I am going to try with keep 2 fact table Fact_Touch_On_Count and Fact_Touch_Off_Counts in my application and see how it goes

Meanwhile, I would like to have your suggestions in handling 1500 millions records efficiently.

Message was edited by: Shivendoo Kumar

1 Reply
Gysbert_Wassenaar
Partner - Champion III
Partner - Champion III

Concatenating your fact tables sounds like a good idea. I don't think you should change that.

Perhaps you can find some useful tips in this discussion: *** 6 Weeks in to QV Development, 30 Million Records QV Document and Help Needed!!! ****


talk is cheap, supply exceeds demand