<?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 ArcSDE Geodatabase Schema Changes &amp; Replication Conflicts in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/arcsde-geodatabase-schema-changes-replication/m-p/755638#M42471</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey,&lt;/P&gt;&lt;P&gt;I've looked through the Help, but haven't found anywhere that answers this question (though I certainly may have missed it).&amp;nbsp; If you have a central ArcSDE enabled database, such as in SQL Server, which has multiple Check Out replicas, I am curious as to what is necessary to make schema changes.&amp;nbsp; If I was to make schema changes (such as adding fields in tables or feature classes), would I need to first check in any outstanding replicas?&amp;nbsp; Or, could I make those changes and check in existing replicas afterwards?&amp;nbsp; I cannot tell if that would be possible, or if the synchronize changes tool would fail to account for those changes and not run.&amp;nbsp; Has anyone dealt with this?&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Justin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 01 Sep 2015 20:03:25 GMT</pubDate>
    <dc:creator>JustinRay1</dc:creator>
    <dc:date>2015-09-01T20:03:25Z</dc:date>
    <item>
      <title>ArcSDE Geodatabase Schema Changes &amp; Replication Conflicts</title>
      <link>https://community.esri.com/t5/data-management-questions/arcsde-geodatabase-schema-changes-replication/m-p/755638#M42471</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey,&lt;/P&gt;&lt;P&gt;I've looked through the Help, but haven't found anywhere that answers this question (though I certainly may have missed it).&amp;nbsp; If you have a central ArcSDE enabled database, such as in SQL Server, which has multiple Check Out replicas, I am curious as to what is necessary to make schema changes.&amp;nbsp; If I was to make schema changes (such as adding fields in tables or feature classes), would I need to first check in any outstanding replicas?&amp;nbsp; Or, could I make those changes and check in existing replicas afterwards?&amp;nbsp; I cannot tell if that would be possible, or if the synchronize changes tool would fail to account for those changes and not run.&amp;nbsp; Has anyone dealt with this?&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Justin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 Sep 2015 20:03:25 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/arcsde-geodatabase-schema-changes-replication/m-p/755638#M42471</guid>
      <dc:creator>JustinRay1</dc:creator>
      <dc:date>2015-09-01T20:03:25Z</dc:date>
    </item>
  </channel>
</rss>

