<?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 Load to temp FGDB or directly to Production Enterprise DB in Data Loading Tools Questions</title>
    <link>https://community.esri.com/t5/data-loading-tools-questions/load-to-temp-fgdb-or-directly-to-production/m-p/1004146#M22</link>
    <description>&lt;P&gt;Curious if there are any opinions or experiences on wether a comprehensive ArcFM geometric network DB should migrate directly into the production Enterprise DB, or if a middle file geodatabase is perhaps a better route. Work everything out in the FGDB and then a streamlined load from FGDB to Enterprise DB? (in theory).&lt;/P&gt;&lt;P&gt;Once the FGDB is finished, export the schema to asset pkg to Enterprise DB (because the load process likely generated some model changes) and the workbooks *should* be able to be pointed to that new Enterprise DB.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 23 Nov 2020 21:53:43 GMT</pubDate>
    <dc:creator>SSMIC3038</dc:creator>
    <dc:date>2020-11-23T21:53:43Z</dc:date>
    <item>
      <title>Load to temp FGDB or directly to Production Enterprise DB</title>
      <link>https://community.esri.com/t5/data-loading-tools-questions/load-to-temp-fgdb-or-directly-to-production/m-p/1004146#M22</link>
      <description>&lt;P&gt;Curious if there are any opinions or experiences on wether a comprehensive ArcFM geometric network DB should migrate directly into the production Enterprise DB, or if a middle file geodatabase is perhaps a better route. Work everything out in the FGDB and then a streamlined load from FGDB to Enterprise DB? (in theory).&lt;/P&gt;&lt;P&gt;Once the FGDB is finished, export the schema to asset pkg to Enterprise DB (because the load process likely generated some model changes) and the workbooks *should* be able to be pointed to that new Enterprise DB.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 23 Nov 2020 21:53:43 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-loading-tools-questions/load-to-temp-fgdb-or-directly-to-production/m-p/1004146#M22</guid>
      <dc:creator>SSMIC3038</dc:creator>
      <dc:date>2020-11-23T21:53:43Z</dc:date>
    </item>
    <item>
      <title>Re: Load to temp FGDB or directly to Production Enterprise DB</title>
      <link>https://community.esri.com/t5/data-loading-tools-questions/load-to-temp-fgdb-or-directly-to-production/m-p/1004716#M23</link>
      <description>&lt;P&gt;Hi Craig,&lt;/P&gt;&lt;P&gt;We would recommend as you've mentioned, the approach to start prototyping with a File Geodatabase until you are satisfied with the data load results in your prototype.&lt;/P&gt;</description>
      <pubDate>Wed, 25 Nov 2020 16:50:52 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-loading-tools-questions/load-to-temp-fgdb-or-directly-to-production/m-p/1004716#M23</guid>
      <dc:creator>AlixVezina</dc:creator>
      <dc:date>2020-11-25T16:50:52Z</dc:date>
    </item>
  </channel>
</rss>

