topic Re: Handling a model having 1500 Millions records for 2 years. What would be best design of App? in QlikView https://community.qlik.com/t5/QlikView/Handling-a-model-having-1500-Millions-records-for-2-years-What/m-p/837470#M294504 <HTML><HEAD></HEAD><BODY><P>Concatenating your fact tables sounds like a good idea. I don't think you should change that. </P><P></P><P>Perhaps you can find some useful tips in this discussion: <A _jive_internal="true" href="https://community.qlik.com/thread/18473" style="font-size: 13px; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3778c7;">*** 6 Weeks in to QV Development, 30 Million Records QV Document and Help Needed!!! ****</A></P></BODY></HTML> Tue, 12 May 2015 07:15:57 GMT Gysbert_Wassenaar 2015-05-12T07:15:57Z Handling a model having 1500 Millions records for 2 years. What would be best design of App? https://community.qlik.com/t5/QlikView/Handling-a-model-having-1500-Millions-records-for-2-years-What/m-p/837469#M294503 <HTML><HEAD></HEAD><BODY><P>Hi All,</P><P></P><P>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.</P><P></P><P>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.</P><P></P><P>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</P><P>and these 2 I am concatenating in my application.</P><P></P><P>Generally Users will seeing count of touch on and off based on date dimension as well as Touch Type.</P><P></P><P>As of Now I am concatenating both the facts data into 1 in my application.</P><P></P><P>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.&nbsp; I have done this but still not much improvement.</P><P></P><P>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</P><P></P><P>Meanwhile, I would like to have your suggestions in handling 1500 millions records efficiently.</P><P></P><P>Message was edited by: Shivendoo Kumar</P></BODY></HTML> Tue, 12 May 2015 01:07:48 GMT https://community.qlik.com/t5/QlikView/Handling-a-model-having-1500-Millions-records-for-2-years-What/m-p/837469#M294503 2015-05-12T01:07:48Z Re: Handling a model having 1500 Millions records for 2 years. What would be best design of App? https://community.qlik.com/t5/QlikView/Handling-a-model-having-1500-Millions-records-for-2-years-What/m-p/837470#M294504 <HTML><HEAD></HEAD><BODY><P>Concatenating your fact tables sounds like a good idea. I don't think you should change that. </P><P></P><P>Perhaps you can find some useful tips in this discussion: <A _jive_internal="true" href="https://community.qlik.com/thread/18473" style="font-size: 13px; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3778c7;">*** 6 Weeks in to QV Development, 30 Million Records QV Document and Help Needed!!! ****</A></P></BODY></HTML> Tue, 12 May 2015 07:15:57 GMT https://community.qlik.com/t5/QlikView/Handling-a-model-having-1500-Millions-records-for-2-years-What/m-p/837470#M294504 Gysbert_Wassenaar 2015-05-12T07:15:57Z