<?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: SAS Audit Trail in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/SAS-Audit-Trail/m-p/35586#M7050</link>
    <description>SAS Audit only works on tables stored in a Base SAS library.&lt;BR /&gt;
If your data needs to be stored in MSSQL, I suggest that you discuss this issue with the MSSQL DBA.&lt;BR /&gt;
&lt;BR /&gt;
/Linus</description>
    <pubDate>Wed, 23 Mar 2011 17:38:47 GMT</pubDate>
    <dc:creator>LinusH</dc:creator>
    <dc:date>2011-03-23T17:38:47Z</dc:date>
    <item>
      <title>SAS Audit Trail</title>
      <link>https://communities.sas.com/t5/SAS-Programming/SAS-Audit-Trail/m-p/35584#M7048</link>
      <description>I wonder if i can apply sas audit trail on MSSQL Data table, i have tried to intiate but fail with error message "ERROR: The HEADER/VARIABLE UPDATE function is not supported by the ODBC engine", does anyone ever done this before?&lt;BR /&gt;
&lt;BR /&gt;
Please shed me some light ! Thanks in advance.</description>
      <pubDate>Tue, 22 Mar 2011 17:25:34 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/SAS-Audit-Trail/m-p/35584#M7048</guid>
      <dc:creator>SASDump</dc:creator>
      <dc:date>2011-03-22T17:25:34Z</dc:date>
    </item>
    <item>
      <title>Re: SAS Audit Trail</title>
      <link>https://communities.sas.com/t5/SAS-Programming/SAS-Audit-Trail/m-p/35585#M7049</link>
      <description>I might ask the question in another way, for using SAS EG 4.3 with MSSQL which audit trail approach should i take? I have basically test with about 3 approaches..namely&lt;BR /&gt;
1. SAS Audit trail - fail with error mentioned&lt;BR /&gt;
2. MSSQL Audit built-in feature (Audit trail log not gd as SAS one; Only can record DML action if submitting with sql statement, if direct edit from dataview of SAS EG the statement capture was filled with parameter which cannot trace the value before/after updating.  )&lt;BR /&gt;
3. Build MSSQL trigger for each table require auditing, so far this is the best but many self maintaining work need to be done.&lt;BR /&gt;
&lt;BR /&gt;
Any has other suggestions?</description>
      <pubDate>Wed, 23 Mar 2011 09:43:32 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/SAS-Audit-Trail/m-p/35585#M7049</guid>
      <dc:creator>SASDump</dc:creator>
      <dc:date>2011-03-23T09:43:32Z</dc:date>
    </item>
    <item>
      <title>Re: SAS Audit Trail</title>
      <link>https://communities.sas.com/t5/SAS-Programming/SAS-Audit-Trail/m-p/35586#M7050</link>
      <description>SAS Audit only works on tables stored in a Base SAS library.&lt;BR /&gt;
If your data needs to be stored in MSSQL, I suggest that you discuss this issue with the MSSQL DBA.&lt;BR /&gt;
&lt;BR /&gt;
/Linus</description>
      <pubDate>Wed, 23 Mar 2011 17:38:47 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/SAS-Audit-Trail/m-p/35586#M7050</guid>
      <dc:creator>LinusH</dc:creator>
      <dc:date>2011-03-23T17:38:47Z</dc:date>
    </item>
    <item>
      <title>Re: SAS Audit Trail</title>
      <link>https://communities.sas.com/t5/SAS-Programming/SAS-Audit-Trail/m-p/35587#M7051</link>
      <description>Thx for your confirmation Linus! Then i will concentrate on my trigger development</description>
      <pubDate>Thu, 24 Mar 2011 09:54:31 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/SAS-Audit-Trail/m-p/35587#M7051</guid>
      <dc:creator>SASDump</dc:creator>
      <dc:date>2011-03-24T09:54:31Z</dc:date>
    </item>
  </channel>
</rss>

