<?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: sasMA creates tables on DB? in SAS Customer Intelligence</title>
    <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/sasMA-creates-tables-on-DB/m-p/306888#M258</link>
    <description>&lt;P&gt;That's correct. Whenever the result of one node is a dataset and it's joined to a select node, or at the end of a campaign when your&amp;nbsp;exports are created, a temporary table is bulkloaded up to the database. If there is an error in the campaign, it's possible those temporary tables are not dropped properly.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;A daily "drop anything in this schema older than 24 hours" script should be safe (unless you have campaigns that take more than 24 hours, in which case I expect you to post another question asking why your campaigns are running so long!). This assumes you are using a dedicated schema (see your business context properties) for your temporary&amp;nbsp;tables. Otherwise you'll need a slightly more surgical approach ("drop anything named T% older than 24 hours").&lt;/P&gt;</description>
    <pubDate>Mon, 24 Oct 2016 16:58:28 GMT</pubDate>
    <dc:creator>shill</dc:creator>
    <dc:date>2016-10-24T16:58:28Z</dc:date>
    <item>
      <title>sasMA creates tables on DB?</title>
      <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/sasMA-creates-tables-on-DB/m-p/306869#M257</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've found some strange tables on DB. Their name is something like "T2140000119HGEF3WMW2VCMTQKZ" (like metadata&amp;nbsp;tables) and each row represent a&amp;nbsp;subject-id defined in SAS MA. It is possible that&amp;nbsp;SAS during campaign execution creates temporary tables on DB (containing the subjectid selected in the&amp;nbsp;select node)&amp;nbsp;and if something&amp;nbsp;goes wrong it can't delete&amp;nbsp;them?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Teresa&lt;/P&gt;</description>
      <pubDate>Mon, 24 Oct 2016 16:22:34 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Customer-Intelligence/sasMA-creates-tables-on-DB/m-p/306869#M257</guid>
      <dc:creator>teresa_abbate</dc:creator>
      <dc:date>2016-10-24T16:22:34Z</dc:date>
    </item>
    <item>
      <title>Re: sasMA creates tables on DB?</title>
      <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/sasMA-creates-tables-on-DB/m-p/306888#M258</link>
      <description>&lt;P&gt;That's correct. Whenever the result of one node is a dataset and it's joined to a select node, or at the end of a campaign when your&amp;nbsp;exports are created, a temporary table is bulkloaded up to the database. If there is an error in the campaign, it's possible those temporary tables are not dropped properly.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;A daily "drop anything in this schema older than 24 hours" script should be safe (unless you have campaigns that take more than 24 hours, in which case I expect you to post another question asking why your campaigns are running so long!). This assumes you are using a dedicated schema (see your business context properties) for your temporary&amp;nbsp;tables. Otherwise you'll need a slightly more surgical approach ("drop anything named T% older than 24 hours").&lt;/P&gt;</description>
      <pubDate>Mon, 24 Oct 2016 16:58:28 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Customer-Intelligence/sasMA-creates-tables-on-DB/m-p/306888#M258</guid>
      <dc:creator>shill</dc:creator>
      <dc:date>2016-10-24T16:58:28Z</dc:date>
    </item>
  </channel>
</rss>

