<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Optimal way to structure a table for a VA dashboard in New SAS User</title>
    <link>https://communities.sas.com/t5/New-SAS-User/Optimal-way-to-structure-a-table-for-a-VA-dashboard/m-p/627162#M20495</link>
    <description>&lt;P&gt;Hello!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a doubt that's more related to optimization by itself than programming. I want to structure a script to extract a table that will be used as the source of a VA dashboard.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The point is that I want to use a great deal of historical data, and if I make a project that process all of it every time it refreshes will take loads of time.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What's the best way to optimize this type of script? I thought about making a first table with all the historical data, and programming the automated project only to process the recent data, appending them together. Is that possible/ideal?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;</description>
    <pubDate>Tue, 25 Feb 2020 12:28:39 GMT</pubDate>
    <dc:creator>Renan_Crepaldi</dc:creator>
    <dc:date>2020-02-25T12:28:39Z</dc:date>
    <item>
      <title>Optimal way to structure a table for a VA dashboard</title>
      <link>https://communities.sas.com/t5/New-SAS-User/Optimal-way-to-structure-a-table-for-a-VA-dashboard/m-p/627162#M20495</link>
      <description>&lt;P&gt;Hello!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a doubt that's more related to optimization by itself than programming. I want to structure a script to extract a table that will be used as the source of a VA dashboard.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The point is that I want to use a great deal of historical data, and if I make a project that process all of it every time it refreshes will take loads of time.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What's the best way to optimize this type of script? I thought about making a first table with all the historical data, and programming the automated project only to process the recent data, appending them together. Is that possible/ideal?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Tue, 25 Feb 2020 12:28:39 GMT</pubDate>
      <guid>https://communities.sas.com/t5/New-SAS-User/Optimal-way-to-structure-a-table-for-a-VA-dashboard/m-p/627162#M20495</guid>
      <dc:creator>Renan_Crepaldi</dc:creator>
      <dc:date>2020-02-25T12:28:39Z</dc:date>
    </item>
    <item>
      <title>Re: Optimal way to structure a table for a VA dashboard</title>
      <link>https://communities.sas.com/t5/New-SAS-User/Optimal-way-to-structure-a-table-for-a-VA-dashboard/m-p/627279#M20514</link>
      <description>&lt;P&gt;Hey, everyone.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I was thinking by myself and I came up with an idea. I could structure a table with all historical data and save it on my library.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;After that, I would build a process that would append the data of the last day. This way, the performance should be really better.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My only doubt is how to build this query, since this append should keep the historical data and overwrite the original table (creating a cycle)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If anyone knows and could help, I'm available to give more details (if necessary)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 25 Feb 2020 18:45:44 GMT</pubDate>
      <guid>https://communities.sas.com/t5/New-SAS-User/Optimal-way-to-structure-a-table-for-a-VA-dashboard/m-p/627279#M20514</guid>
      <dc:creator>Renan_Crepaldi</dc:creator>
      <dc:date>2020-02-25T18:45:44Z</dc:date>
    </item>
    <item>
      <title>Re: Optimal way to structure a table for a VA dashboard</title>
      <link>https://communities.sas.com/t5/New-SAS-User/Optimal-way-to-structure-a-table-for-a-VA-dashboard/m-p/628746#M20675</link>
      <description>&lt;P&gt;Hello, everyone!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;After doing some research on the web and talking with my working partners, I ended up finding a way to structure this table.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;First, I constructed a table with all the historical data, adding the calculated fields I needed. Then I made a query that consults the max date of the historical table, filtering all the data that's greater than this max date, and inserts them on the historical table.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I don't know if this is the best way in performance, but it's running pretty fast.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyway, if someone knows a better format to do this type of script, I'm open for suggestions.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Mon, 02 Mar 2020 12:31:58 GMT</pubDate>
      <guid>https://communities.sas.com/t5/New-SAS-User/Optimal-way-to-structure-a-table-for-a-VA-dashboard/m-p/628746#M20675</guid>
      <dc:creator>Renan_Crepaldi</dc:creator>
      <dc:date>2020-03-02T12:31:58Z</dc:date>
    </item>
  </channel>
</rss>

