<?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: Step by Step instructions for adding a topology to an SDE database dataset that has versions and distributed data. in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/step-by-step-instructions-for-adding-a-topology-to/m-p/689694#M39089</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Probably not what you are looking for but I stay away from feature datasets in the SDE environment.&amp;nbsp; They have a tendency to misbehave.&amp;nbsp; My experience (going back to v. 8.0) with multiple versions has been less than stellar as well: when it comes to reconciling it about drove me mad trying to unravel conflicts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That said, my experience with replication has mostly been outstanding: you might want to look at one way replication to a file geodatabase and let the feature datasets and topologies reside there.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just my $00.02....&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 20 Jan 2015 13:28:52 GMT</pubDate>
    <dc:creator>JoeBorgione</dc:creator>
    <dc:date>2015-01-20T13:28:52Z</dc:date>
    <item>
      <title>Step by Step instructions for adding a topology to an SDE database dataset that has versions and distributed data.</title>
      <link>https://community.esri.com/t5/data-management-questions/step-by-step-instructions-for-adding-a-topology-to/m-p/689693#M39088</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We set up an SDE database with 3 versions and 1 2- way distributed version.&amp;nbsp; We later decided that we would like some of the distibuted data that is in a feature dataset to participate in a topology. &lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am searching for the best practices way to add the topology to the parent database&amp;nbsp; with a little pain as possible. I would prefer to not have to recreate my distributed dataset.&amp;nbsp; I have some ideas, but I would welcome suggestions from an experienced user. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Jan 2015 22:27:47 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/step-by-step-instructions-for-adding-a-topology-to/m-p/689693#M39088</guid>
      <dc:creator>deleted-user-rmQdIupSdOqe</dc:creator>
      <dc:date>2015-01-19T22:27:47Z</dc:date>
    </item>
    <item>
      <title>Re: Step by Step instructions for adding a topology to an SDE database dataset that has versions and distributed data.</title>
      <link>https://community.esri.com/t5/data-management-questions/step-by-step-instructions-for-adding-a-topology-to/m-p/689694#M39089</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Probably not what you are looking for but I stay away from feature datasets in the SDE environment.&amp;nbsp; They have a tendency to misbehave.&amp;nbsp; My experience (going back to v. 8.0) with multiple versions has been less than stellar as well: when it comes to reconciling it about drove me mad trying to unravel conflicts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That said, my experience with replication has mostly been outstanding: you might want to look at one way replication to a file geodatabase and let the feature datasets and topologies reside there.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just my $00.02....&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Jan 2015 13:28:52 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/step-by-step-instructions-for-adding-a-topology-to/m-p/689694#M39089</guid>
      <dc:creator>JoeBorgione</dc:creator>
      <dc:date>2015-01-20T13:28:52Z</dc:date>
    </item>
  </channel>
</rss>

