<?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: Multiple geodatabase vs Single Geodatabase (in 1 Orcl instance) in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/multiple-geodatabase-vs-single-geodatabase-in-1/m-p/69162#M3991</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;A href="http://resources.arcgis.com/gallery/file/geodatabase/details?entryID=F227ACA4-1422-2418-348C-85F7B88C73FE"&gt;Guide to user-schema geodatabases in Oracle&lt;/A&gt;&lt;SPAN&gt;, though I profoundly disagree with the &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;"benefit" of separating development and production data -- for this, multiple Oracle&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;instances are required.&amp;nbsp; All the drawbacks are in the "rules," they're just not listed&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;as drawbacks.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;- V&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 23 Oct 2012 11:39:16 GMT</pubDate>
    <dc:creator>VinceAngelo</dc:creator>
    <dc:date>2012-10-23T11:39:16Z</dc:date>
    <item>
      <title>Multiple geodatabase vs Single Geodatabase (in 1 Orcl instance)</title>
      <link>https://community.esri.com/t5/data-management-questions/multiple-geodatabase-vs-single-geodatabase-in-1/m-p/69161#M3990</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Dear experts,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;What is the advantage of single geodb over multiple geodb in 1 Orcl instance (from many aspects such as backing up, upgrading and performance etc) ? &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Can some one point me to an article or whatever source on the web so i can use them as evidence.... ?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Many thanks&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Oct 2012 10:32:42 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/multiple-geodatabase-vs-single-geodatabase-in-1/m-p/69161#M3990</guid>
      <dc:creator>HaniuHokkaido</dc:creator>
      <dc:date>2012-10-23T10:32:42Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple geodatabase vs Single Geodatabase (in 1 Orcl instance)</title>
      <link>https://community.esri.com/t5/data-management-questions/multiple-geodatabase-vs-single-geodatabase-in-1/m-p/69162#M3991</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;A href="http://resources.arcgis.com/gallery/file/geodatabase/details?entryID=F227ACA4-1422-2418-348C-85F7B88C73FE"&gt;Guide to user-schema geodatabases in Oracle&lt;/A&gt;&lt;SPAN&gt;, though I profoundly disagree with the &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;"benefit" of separating development and production data -- for this, multiple Oracle&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;instances are required.&amp;nbsp; All the drawbacks are in the "rules," they're just not listed&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;as drawbacks.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;- V&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Oct 2012 11:39:16 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/multiple-geodatabase-vs-single-geodatabase-in-1/m-p/69162#M3991</guid>
      <dc:creator>VinceAngelo</dc:creator>
      <dc:date>2012-10-23T11:39:16Z</dc:date>
    </item>
  </channel>
</rss>

