<?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: Traditional Versioning Replication with Edits to Base in Geodatabase Questions</title>
    <link>https://community.esri.com/t5/geodatabase-questions/traditional-versioning-replication-with-edits-to/m-p/1382821#M8882</link>
    <description>&lt;P&gt;Hey &lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/138089"&gt;@RobertKrisher&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for the response! I was also curious if you knew, we found that the database when traditionally versioned without moving to base, it has a SDE_STATE_ID, in what case would that state ID change?&lt;/P&gt;&lt;P&gt;Thanks again!&lt;/P&gt;&lt;P&gt;Cody&lt;/P&gt;</description>
    <pubDate>Thu, 15 Feb 2024 14:53:00 GMT</pubDate>
    <dc:creator>CodyPatterson</dc:creator>
    <dc:date>2024-02-15T14:53:00Z</dc:date>
    <item>
      <title>Traditional Versioning Replication with Edits to Base</title>
      <link>https://community.esri.com/t5/geodatabase-questions/traditional-versioning-replication-with-edits-to/m-p/1382807#M8878</link>
      <description>&lt;P&gt;Hey All,&lt;/P&gt;&lt;P&gt;We view our data through SQL, and would like to replicate our Geodatabase one way to another geodatabase, how can we accomplish this while also being able to view our data from SQL as replication does not allow the moving of edits to the base?&lt;/P&gt;&lt;P&gt;Enterprise 11.2 geodatabase&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;&lt;P&gt;Cody&lt;/P&gt;</description>
      <pubDate>Thu, 15 Feb 2024 14:32:21 GMT</pubDate>
      <guid>https://community.esri.com/t5/geodatabase-questions/traditional-versioning-replication-with-edits-to/m-p/1382807#M8878</guid>
      <dc:creator>CodyPatterson</dc:creator>
      <dc:date>2024-02-15T14:32:21Z</dc:date>
    </item>
    <item>
      <title>Re: Traditional Versioning Replication with Edits to Base</title>
      <link>https://community.esri.com/t5/geodatabase-questions/traditional-versioning-replication-with-edits-to/m-p/1382813#M8880</link>
      <description>&lt;P&gt;Even though the edits aren't moved to the base tables you can still query the data using SQL. You'll just need to use versioned views to query the data in default (or other versions). You can find examples of this technique in &lt;A href="https://desktop.arcgis.com/en/arcmap/latest/manage-data/using-sql-with-gdbs/read-sqlserver-versioned-data-with-sql.htm" target="_blank" rel="noopener"&gt;this page of the online help&lt;/A&gt;. These versioned views will do the hard work of joining together all the edits in the base, adds, and delete tables to show you the correct rows.&lt;/P&gt;</description>
      <pubDate>Thu, 15 Feb 2024 14:39:45 GMT</pubDate>
      <guid>https://community.esri.com/t5/geodatabase-questions/traditional-versioning-replication-with-edits-to/m-p/1382813#M8880</guid>
      <dc:creator>RobertKrisher</dc:creator>
      <dc:date>2024-02-15T14:39:45Z</dc:date>
    </item>
    <item>
      <title>Re: Traditional Versioning Replication with Edits to Base</title>
      <link>https://community.esri.com/t5/geodatabase-questions/traditional-versioning-replication-with-edits-to/m-p/1382821#M8882</link>
      <description>&lt;P&gt;Hey &lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/138089"&gt;@RobertKrisher&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for the response! I was also curious if you knew, we found that the database when traditionally versioned without moving to base, it has a SDE_STATE_ID, in what case would that state ID change?&lt;/P&gt;&lt;P&gt;Thanks again!&lt;/P&gt;&lt;P&gt;Cody&lt;/P&gt;</description>
      <pubDate>Thu, 15 Feb 2024 14:53:00 GMT</pubDate>
      <guid>https://community.esri.com/t5/geodatabase-questions/traditional-versioning-replication-with-edits-to/m-p/1382821#M8882</guid>
      <dc:creator>CodyPatterson</dc:creator>
      <dc:date>2024-02-15T14:53:00Z</dc:date>
    </item>
    <item>
      <title>Re: Traditional Versioning Replication with Edits to Base</title>
      <link>https://community.esri.com/t5/geodatabase-questions/traditional-versioning-replication-with-edits-to/m-p/1382833#M8883</link>
      <description>&lt;P&gt;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/712076"&gt;@CodyPatterson&lt;/a&gt;&amp;nbsp;As soon as something is traditionally versioned it will get an SDE_STATE_ID field (regardless of whether edits are moved to base) and this value is used along with several system-maintained tables to manage all the edits in default and versions. If you just use the versioned views, you don't need to worry too much about what's happening behind the scenes (because the views handle it all for you).&lt;/P&gt;&lt;P&gt;There are several technical articles out there that explain this process (and the waters can get pretty deep on this stuff)&lt;/P&gt;&lt;P&gt;Here's a good introduction to traditional versioning:&amp;nbsp;&lt;A href="https://community.esri.com/t5/data-management-documents/versioning-101-arcuser-technical-article/ta-p/909939" target="_blank"&gt;Versioning 101 - ArcUser Technical Article - Esri Community&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Here's a description of the system tables:&amp;nbsp;&lt;A href="https://resources.arcgis.com/en/help/main/10.1/index.html#//002q0000007v000000" target="_blank"&gt;ArcGIS Help 10.1 - Versioned tables in a geodatabase in SQL Server&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 15 Feb 2024 15:08:15 GMT</pubDate>
      <guid>https://community.esri.com/t5/geodatabase-questions/traditional-versioning-replication-with-edits-to/m-p/1382833#M8883</guid>
      <dc:creator>RobertKrisher</dc:creator>
      <dc:date>2024-02-15T15:08:15Z</dc:date>
    </item>
    <item>
      <title>Re: Traditional Versioning Replication with Edits to Base</title>
      <link>https://community.esri.com/t5/geodatabase-questions/traditional-versioning-replication-with-edits-to/m-p/1382884#M8886</link>
      <description>&lt;P&gt;Hey &lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/138089"&gt;@RobertKrisher&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I think that answers most of my questions, I appreciate the resources greatly!&lt;/P&gt;&lt;P&gt;Cody&lt;/P&gt;</description>
      <pubDate>Thu, 15 Feb 2024 16:13:57 GMT</pubDate>
      <guid>https://community.esri.com/t5/geodatabase-questions/traditional-versioning-replication-with-edits-to/m-p/1382884#M8886</guid>
      <dc:creator>CodyPatterson</dc:creator>
      <dc:date>2024-02-15T16:13:57Z</dc:date>
    </item>
    <item>
      <title>Re: Traditional Versioning Replication with Edits to Base</title>
      <link>https://community.esri.com/t5/geodatabase-questions/traditional-versioning-replication-with-edits-to/m-p/1382885#M8887</link>
      <description>&lt;P&gt;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/712076"&gt;@CodyPatterson&lt;/a&gt;&amp;nbsp;glad I was able to help!&lt;/P&gt;</description>
      <pubDate>Thu, 15 Feb 2024 16:14:42 GMT</pubDate>
      <guid>https://community.esri.com/t5/geodatabase-questions/traditional-versioning-replication-with-edits-to/m-p/1382885#M8887</guid>
      <dc:creator>RobertKrisher</dc:creator>
      <dc:date>2024-02-15T16:14:42Z</dc:date>
    </item>
  </channel>
</rss>

