<?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 Re: One big data set or multiple data sets in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/One-big-data-set-or-multiple-data-sets/m-p/484302#M125738</link>
    <description>&lt;P&gt;If your queries/reports are mainly run for single months, it makes sense (performancewise) to keep the datasets separate.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 06 Aug 2018 10:11:31 GMT</pubDate>
    <dc:creator>Kurt_Bremser</dc:creator>
    <dc:date>2018-08-06T10:11:31Z</dc:date>
    <item>
      <title>One big data set or multiple data sets</title>
      <link>https://communities.sas.com/t5/SAS-Programming/One-big-data-set-or-multiple-data-sets/m-p/484301#M125737</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;I want to ask a question about efficiency.&lt;/P&gt;&lt;P&gt;In my work every month a data set (raw data) of Loans balances is created.&lt;/P&gt;&lt;P&gt;What &amp;nbsp;is more&amp;nbsp;&lt;SPAN&gt;efficiency way:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;option1- Every month create another raw data data set&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;option2- Every month &amp;nbsp;add new rows &amp;nbsp;to the previous month data set.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;What do you think is a better way to do it?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Why?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;You need to know that lots of queries will be written based on these raw data tables.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Joe&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 06 Aug 2018 10:05:17 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/One-big-data-set-or-multiple-data-sets/m-p/484301#M125737</guid>
      <dc:creator>Ronein</dc:creator>
      <dc:date>2018-08-06T10:05:17Z</dc:date>
    </item>
    <item>
      <title>Re: One big data set or multiple data sets</title>
      <link>https://communities.sas.com/t5/SAS-Programming/One-big-data-set-or-multiple-data-sets/m-p/484302#M125738</link>
      <description>&lt;P&gt;If your queries/reports are mainly run for single months, it makes sense (performancewise) to keep the datasets separate.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 06 Aug 2018 10:11:31 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/One-big-data-set-or-multiple-data-sets/m-p/484302#M125738</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2018-08-06T10:11:31Z</dc:date>
    </item>
    <item>
      <title>Re: One big data set or multiple data sets</title>
      <link>https://communities.sas.com/t5/SAS-Programming/One-big-data-set-or-multiple-data-sets/m-p/484303#M125739</link>
      <description>&lt;P&gt;Splitting same data is rarely a good idea.&amp;nbsp; Think of it this way, if you have multiple datasets split by date you:&lt;/P&gt;
&lt;P&gt;1) have lots more files with their own header block - takes more space&lt;/P&gt;
&lt;P&gt;2) have to write messy code to process lots of different dataset names - takes more time an resources to do so and is less stable&lt;/P&gt;
&lt;P&gt;3) have code which is opening, closing, writing etc. data lots of times, inefficient for processing power&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hence the conclusion I would come to is no, don't split the data out into sections, have one single table with a fixed simple structure which is very easy to program against, query etc.&amp;nbsp; Just look at how the big databases do it, Oracle has a few tables with simple structures to hold lots of data.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As a bit of a disclaimer, this&amp;nbsp;is general, if your looking at something more specific like big data, or disparate data then there are other models for such a thing.&amp;nbsp; But in general, for most tasks, keep it simple, keep it generic.&lt;/P&gt;</description>
      <pubDate>Mon, 06 Aug 2018 10:13:36 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/One-big-data-set-or-multiple-data-sets/m-p/484303#M125739</guid>
      <dc:creator>RW9</dc:creator>
      <dc:date>2018-08-06T10:13:36Z</dc:date>
    </item>
  </channel>
</rss>

