<?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 Audit Trail in SAS Health and Life Sciences</title>
    <link>https://communities.sas.com/t5/SAS-Health-and-Life-Sciences/Audit-Trail/m-p/5105#M430</link>
    <description>Hello!&lt;BR /&gt;
&lt;BR /&gt;
I am thinking about implementing an audit trail on MySQL which would work with triggers. Does somebody know if the triggers work when I do an SQL update/insert/delete statement directly from SAS to MySQL? &lt;BR /&gt;
&lt;BR /&gt;
Thanks!</description>
    <pubDate>Wed, 17 Oct 2007 10:56:16 GMT</pubDate>
    <dc:creator>JuanVte</dc:creator>
    <dc:date>2007-10-17T10:56:16Z</dc:date>
    <item>
      <title>Audit Trail</title>
      <link>https://communities.sas.com/t5/SAS-Health-and-Life-Sciences/Audit-Trail/m-p/5105#M430</link>
      <description>Hello!&lt;BR /&gt;
&lt;BR /&gt;
I am thinking about implementing an audit trail on MySQL which would work with triggers. Does somebody know if the triggers work when I do an SQL update/insert/delete statement directly from SAS to MySQL? &lt;BR /&gt;
&lt;BR /&gt;
Thanks!</description>
      <pubDate>Wed, 17 Oct 2007 10:56:16 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Health-and-Life-Sciences/Audit-Trail/m-p/5105#M430</guid>
      <dc:creator>JuanVte</dc:creator>
      <dc:date>2007-10-17T10:56:16Z</dc:date>
    </item>
    <item>
      <title>Re: Audit Trail</title>
      <link>https://communities.sas.com/t5/SAS-Health-and-Life-Sciences/Audit-Trail/m-p/5106#M431</link>
      <description>They should, but you may want to consider doing the audit trail a different way as triggers can slow down your performance significantly.&lt;BR /&gt;
&lt;BR /&gt;
If you can grab the audit information (userID, date, etc...) prior to doing the insert/update, then you could put that information into the SQL statement and not rely on the database to do the work.</description>
      <pubDate>Mon, 28 Jan 2008 22:38:41 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Health-and-Life-Sciences/Audit-Trail/m-p/5106#M431</guid>
      <dc:creator>JasonDiVirgilio</dc:creator>
      <dc:date>2008-01-28T22:38:41Z</dc:date>
    </item>
  </channel>
</rss>

