<?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 SQL Triggers on versioned data in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/sql-triggers-on-versioned-data/m-p/93570#M5507</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I am trying to avoid future problems, so I thought I'd better ask about using SQL programability with a SDE database. What problems (if any) can I incur by using triggers, functions, and stored procedures with versioned SDE data?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If it would be helpful, I could give some specifics on the project I'm working on.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 18 Jul 2011 12:38:58 GMT</pubDate>
    <dc:creator>DougKampe</dc:creator>
    <dc:date>2011-07-18T12:38:58Z</dc:date>
    <item>
      <title>SQL Triggers on versioned data</title>
      <link>https://community.esri.com/t5/data-management-questions/sql-triggers-on-versioned-data/m-p/93570#M5507</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I am trying to avoid future problems, so I thought I'd better ask about using SQL programability with a SDE database. What problems (if any) can I incur by using triggers, functions, and stored procedures with versioned SDE data?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If it would be helpful, I could give some specifics on the project I'm working on.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 Jul 2011 12:38:58 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/sql-triggers-on-versioned-data/m-p/93570#M5507</guid>
      <dc:creator>DougKampe</dc:creator>
      <dc:date>2011-07-18T12:38:58Z</dc:date>
    </item>
    <item>
      <title>Re: SQL Triggers on versioned data</title>
      <link>https://community.esri.com/t5/data-management-questions/sql-triggers-on-versioned-data/m-p/93571#M5508</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi Doug,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Depend on what kind of triggers you want to set, put a trigger on a versioned FC can be problematic. A while ago, one of our developers put a trigger on a FC for a test. The FC's maintenance people reported that they recieved errors they never had before and couldn't finished their editing work. As a SDE administrator, I also encountered error message while doing SDE compression, even the compression seemed finishing well. Remove the trigger solved all porblems. It could be just some privilege issue, but we never bother to dig into.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;My suggestion would be&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;1. If you DON'T have to put a trigger on a versioned FC, don't do it! There should be plenty of other ways to do the same thing.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;2. If you absolutely need it, do a thorough testing before move to production.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Robert&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Jul 2011 14:33:21 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/sql-triggers-on-versioned-data/m-p/93571#M5508</guid>
      <dc:creator>RobertHu</dc:creator>
      <dc:date>2011-07-19T14:33:21Z</dc:date>
    </item>
  </channel>
</rss>

