<?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 Alternatives for One-Way Replicas? in Implementing ArcGIS Questions</title>
    <link>https://community.esri.com/t5/implementing-arcgis-questions/alternatives-for-one-way-replicas/m-p/726588#M648</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm looking for a simplified approach for maintaining a read-only File Geodatabase.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is my scenario:&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;1 Master Database made up of 50 contributors.&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;I need to have a File Geodatabase to serve essentially as a backup stored at each contributor's location.&lt;/LI&gt;&lt;LI&gt;Data has to be filtered to them based on a field designating the contributor's ID. (One person can't have&amp;nbsp;access to a copy of the Master)&lt;/LI&gt;&lt;LI&gt;Creating 50 One-Way Replicas seems like overkill and a lot of overhead to maintain for both the synchronizing process as well as the database schema of the master will change throughout each year.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are there alternative options out there maybe scripting or SQL dumps or something I can look into?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the assistance!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 27 Nov 2018 16:47:53 GMT</pubDate>
    <dc:creator>Matt-Huser</dc:creator>
    <dc:date>2018-11-27T16:47:53Z</dc:date>
    <item>
      <title>Alternatives for One-Way Replicas?</title>
      <link>https://community.esri.com/t5/implementing-arcgis-questions/alternatives-for-one-way-replicas/m-p/726588#M648</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm looking for a simplified approach for maintaining a read-only File Geodatabase.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is my scenario:&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;1 Master Database made up of 50 contributors.&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;I need to have a File Geodatabase to serve essentially as a backup stored at each contributor's location.&lt;/LI&gt;&lt;LI&gt;Data has to be filtered to them based on a field designating the contributor's ID. (One person can't have&amp;nbsp;access to a copy of the Master)&lt;/LI&gt;&lt;LI&gt;Creating 50 One-Way Replicas seems like overkill and a lot of overhead to maintain for both the synchronizing process as well as the database schema of the master will change throughout each year.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are there alternative options out there maybe scripting or SQL dumps or something I can look into?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the assistance!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Nov 2018 16:47:53 GMT</pubDate>
      <guid>https://community.esri.com/t5/implementing-arcgis-questions/alternatives-for-one-way-replicas/m-p/726588#M648</guid>
      <dc:creator>Matt-Huser</dc:creator>
      <dc:date>2018-11-27T16:47:53Z</dc:date>
    </item>
  </channel>
</rss>

