<?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 From Versioned Table to Non-Versioned in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/from-versioned-table-to-non-versioned/m-p/477650#M27204</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I am using ESRI 9.3.1 with Oracle 11G.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I have one feature class and one sde table. Both are versioned.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Because of multi user editing , data in sde table is getting duplicated and I don't see any straight way to resolve that?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;One option I see is to convert the sde table to non-versioned and have some primary key.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Is it a good practice to have non-versioned table with versioned table in transcation environment?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Any other idea or any disadvantage of doing that other than I am taking out versioning capability from that table and hence undo operation too.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 20 Dec 2011 06:05:32 GMT</pubDate>
    <dc:creator>ManojGarg</dc:creator>
    <dc:date>2011-12-20T06:05:32Z</dc:date>
    <item>
      <title>From Versioned Table to Non-Versioned</title>
      <link>https://community.esri.com/t5/data-management-questions/from-versioned-table-to-non-versioned/m-p/477650#M27204</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I am using ESRI 9.3.1 with Oracle 11G.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I have one feature class and one sde table. Both are versioned.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Because of multi user editing , data in sde table is getting duplicated and I don't see any straight way to resolve that?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;One option I see is to convert the sde table to non-versioned and have some primary key.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Is it a good practice to have non-versioned table with versioned table in transcation environment?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Any other idea or any disadvantage of doing that other than I am taking out versioning capability from that table and hence undo operation too.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Dec 2011 06:05:32 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/from-versioned-table-to-non-versioned/m-p/477650#M27204</guid>
      <dc:creator>ManojGarg</dc:creator>
      <dc:date>2011-12-20T06:05:32Z</dc:date>
    </item>
  </channel>
</rss>

