https://communities.sas.com/t5/SAS-Visual-Analytics/How-to-organize-effectively-diverse-data-needed-for-a-dashboard/m-p/470432#M10470 <P>If there is no commonality between the tables then I suggest keeping them separate is sensible. It is quite easy to build batch processes that load LASR tables automatically so I don't see managing a lot of tables is a problem.</P> Thu, 14 Jun 2018 20:09:40 GMT SASKiwi 2018-06-14T20:09:40Z https://communities.sas.com/t5/SAS-Visual-Analytics/How-to-organize-effectively-diverse-data-needed-for-a-dashboard/m-p/469768#M10446 <P>Hi,</P><P>I have to make a dashboard to monitor some business processes. Processes are quite diverse, so the data needed is not standardized. If I just loaded all the data needed to separate tables, it would be &gt; 30 tables, and their count will grow over time.</P><P>&nbsp;</P><P><STRONG>So the question is – how to organize diverse data for a dashboard? Is there any kind of best-practice? </STRONG></P><P>&nbsp;</P><P>Considering Qlik Sense, I thought about using just one "key-value" table on an Oracle server. In this case each dashboard report could be based on a special sql-code, which takes filtered data from the table and transforms it from "key-value" to a usual table on-the-fly (this could be quite fast if the data table on a server is partitioned by a process/report name).</P><P>&nbsp;</P><P>But we decided to build our reports in SAS VA, and it seems key-value solution is not appropriate for SAS VA because of in-memory calculation (key-value structure may increases data size) and poorer abilities to manage key-value data (not sure).</P><P>&nbsp;</P><P><STRONG>So, is there any elegant solution to organize the data?</STRONG></P><P><STRONG>I would appreciate any ideas.</STRONG></P> Tue, 12 Jun 2018 21:35:54 GMT https://communities.sas.com/t5/SAS-Visual-Analytics/How-to-organize-effectively-diverse-data-needed-for-a-dashboard/m-p/469768#M10446 sazonov-nv 2018-06-12T21:35:54Z https://communities.sas.com/t5/SAS-Visual-Analytics/How-to-organize-effectively-diverse-data-needed-for-a-dashboard/m-p/469842#M10450 <P>It is perfectly OK to have multiple data sources for one VA report. Having over 30 data sources for a single report sounds a lot. Would it make sense to split your dashboard into more than one VA report?</P> <P>&nbsp;</P> <P>Also are there any similarities between some of the data sources so you can combine these? Many data sources are likely to slow down your report and if you add a lot of calculated items then that will slow it even more.</P> <P>&nbsp;</P> <P>Providing good VA report performance is a balance between not overloading the report with too many objects (which are hard to understand anyway) and keeping data sources efficient with only the essential columns and calculated items.</P> <P>&nbsp;</P> <P>&nbsp;</P> Wed, 13 Jun 2018 07:10:07 GMT https://communities.sas.com/t5/SAS-Visual-Analytics/How-to-organize-effectively-diverse-data-needed-for-a-dashboard/m-p/469842#M10450 SASKiwi 2018-06-13T07:10:07Z https://communities.sas.com/t5/SAS-Visual-Analytics/How-to-organize-effectively-diverse-data-needed-for-a-dashboard/m-p/470273#M10465 <P><a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/13976">@SASKiwi</a>, thank you for your reply.</P><P>&nbsp;</P><P>It may be a multiple-sheet report (with one main sheet for navigation) or several reports, but in this case they still have to be linked to&nbsp;be considered by users as one solid platform (users want simple navigation without any borders between reports).&nbsp;I think it's not critical, but still I hope to organize some way all the data needed to avoid problems with maintaning / updating many tables.&nbsp;</P><P>&nbsp;</P><P>Similarities are very week (one can say 'proccess name' and 'report date' are the only common fields).</P> Thu, 14 Jun 2018 12:14:04 GMT https://communities.sas.com/t5/SAS-Visual-Analytics/How-to-organize-effectively-diverse-data-needed-for-a-dashboard/m-p/470273#M10465 sazonov-nv 2018-06-14T12:14:04Z https://communities.sas.com/t5/SAS-Visual-Analytics/How-to-organize-effectively-diverse-data-needed-for-a-dashboard/m-p/470301#M10466 <P>We have many customers who create reports that are used to enable users to navigate to other reports. If you move forward with this plan, I would suggest creating separate reports. You can link to the reports just as easily as linking to sections in the same report, but performance should be better.</P> Thu, 14 Jun 2018 13:23:44 GMT https://communities.sas.com/t5/SAS-Visual-Analytics/How-to-organize-effectively-diverse-data-needed-for-a-dashboard/m-p/470301#M10466 Madelyn_SAS 2018-06-14T13:23:44Z https://communities.sas.com/t5/SAS-Visual-Analytics/How-to-organize-effectively-diverse-data-needed-for-a-dashboard/m-p/470355#M10468 <a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/13745">@Madelyn_SAS</a>, thanks, I'll probably follow this recommendation. But still I have more concerns about not the report itself, but about data organization. Is there any best-practice to organize the data, or using a lot of separate tables is the only appropriate way?<BR />Thanks in advance. Thu, 14 Jun 2018 15:48:06 GMT https://communities.sas.com/t5/SAS-Visual-Analytics/How-to-organize-effectively-diverse-data-needed-for-a-dashboard/m-p/470355#M10468 sazonov-nv 2018-06-14T15:48:06Z https://communities.sas.com/t5/SAS-Visual-Analytics/How-to-organize-effectively-diverse-data-needed-for-a-dashboard/m-p/470432#M10470 <P>If there is no commonality between the tables then I suggest keeping them separate is sensible. It is quite easy to build batch processes that load LASR tables automatically so I don't see managing a lot of tables is a problem.</P> Thu, 14 Jun 2018 20:09:40 GMT https://communities.sas.com/t5/SAS-Visual-Analytics/How-to-organize-effectively-diverse-data-needed-for-a-dashboard/m-p/470432#M10470 SASKiwi 2018-06-14T20:09:40Z