<?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: Moving Geodatabase  to Oracle Database in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/moving-geodatabase-to-oracle-database/m-p/45196#M2539</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Yes and no, of course.&amp;nbsp; All Esri tools work with all supported enterprise servers, but that&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;doesn't mean that a file geodatabase filled with reserved words for table and column&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;names will load in every (or any) database.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;It's generally better to design a geodatabase in the RDBMS of choice, to avoid the&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;issues that occur when porting.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;- V&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 31 Oct 2013 11:41:09 GMT</pubDate>
    <dc:creator>VinceAngelo</dc:creator>
    <dc:date>2013-10-31T11:41:09Z</dc:date>
    <item>
      <title>Moving Geodatabase  to Oracle Database</title>
      <link>https://community.esri.com/t5/data-management-questions/moving-geodatabase-to-oracle-database/m-p/45195#M2538</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Just wondering is there a process in place to convert any geodatabase created to a oracle/sql server database? Preferably a oracle database. I have created the geodatabase but now hoping to put into a table in oracle.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thank you&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Oct 2013 08:24:56 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/moving-geodatabase-to-oracle-database/m-p/45195#M2538</guid>
      <dc:creator>FaisalKhan3</dc:creator>
      <dc:date>2013-10-31T08:24:56Z</dc:date>
    </item>
    <item>
      <title>Re: Moving Geodatabase  to Oracle Database</title>
      <link>https://community.esri.com/t5/data-management-questions/moving-geodatabase-to-oracle-database/m-p/45196#M2539</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Yes and no, of course.&amp;nbsp; All Esri tools work with all supported enterprise servers, but that&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;doesn't mean that a file geodatabase filled with reserved words for table and column&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;names will load in every (or any) database.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;It's generally better to design a geodatabase in the RDBMS of choice, to avoid the&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;issues that occur when porting.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;- V&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Oct 2013 11:41:09 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/moving-geodatabase-to-oracle-database/m-p/45196#M2539</guid>
      <dc:creator>VinceAngelo</dc:creator>
      <dc:date>2013-10-31T11:41:09Z</dc:date>
    </item>
    <item>
      <title>Re: Moving Geodatabase  to Oracle Database</title>
      <link>https://community.esri.com/t5/data-management-questions/moving-geodatabase-to-oracle-database/m-p/45197#M2540</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Are you talking about creating a FDGB and then moving into an RDBMS, or are you talking about "converting" an Oracle GDB to a SQL Server GDB (or vice versa)?&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;ArcGIS Diagrammer is a free tool that allows you to craft your geodatabase model in an environment agnostic to a specific RDBMS.&amp;nbsp; I've had good luck with this tool from time to time from a basic design standpoint where I can create tables, feature classes, rasters, relationship classes, and other Esri-related objects.&amp;nbsp; It's a handy tool for quickly modifying the order of fields and their names, too.&amp;nbsp; Once you save your project file, you'll be able to export a schema XML document which can then be imported into an enterprise geodatabase in SQL Server or Oracle (or a FGDB if you chose).&amp;nbsp; This really isn't "converting" the database from SQL Server to Oracle or vice versa (that is, keeping your data intact), but it does give you flexibility to manufacture a data model and load its empty schema wherever you desire.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;That being said, if you need a way to move your data from one RDBMS to another (which may not be what you're trying to do, I can't be sure), you may be able to simply use a manual copy and paste the objects from one geodatabase (let's say, Oracle) into another geodatabase (SQL Server) if you establish connections to both in ArcCatalog.&amp;nbsp; (Note: The Copy Data tool won't work in the case where relationship classes are involved whereby one object class is related to more than one other object class.)&amp;nbsp; You undoubtedly will have to work through granting your permissions on the target afterward, though.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 15 Dec 2013 20:34:47 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/moving-geodatabase-to-oracle-database/m-p/45197#M2540</guid>
      <dc:creator>WilliamCraft</dc:creator>
      <dc:date>2013-12-15T20:34:47Z</dc:date>
    </item>
  </channel>
</rss>

