<?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: Tablespace size in Geodatabase Questions</title>
    <link>https://community.esri.com/t5/geodatabase-questions/tablespace-size/m-p/858518#M5609</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You should not ever have any spatial data in the SDE tablespace (it should be exclusively reserved for geodatabase metadata tables), so the quota on SDE should not in any way be impacted by geometry storage migration.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would not recommend &lt;EM&gt;in-situ&lt;/EM&gt; geometry migration (the process does significant damage to the base table [through fragmentation and high water mark creep]).&amp;nbsp; If you need to recreate the tables for performance reasons, then you might as well create new tablespaces to manage them as neatly as possible (provide for storage increase by setting a quota 50% larger than the previous usage, then reducing it when the smoke clears.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.esri.com/thread/162136"&gt;Another recent thread&lt;/A&gt; discussed this same issue, so I recommend you review the spatial defragmentation recommendation as well.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 15 Jul 2015 17:28:00 GMT</pubDate>
    <dc:creator>VinceAngelo</dc:creator>
    <dc:date>2015-07-15T17:28:00Z</dc:date>
    <item>
      <title>Tablespace size</title>
      <link>https://community.esri.com/t5/geodatabase-questions/tablespace-size/m-p/858516#M5607</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, I need to know what quota I need to give to tablespace.s I'm migrating from sdebinary to st_geometry and I'm having problema with the tablespace size. I have read that I need to grant &lt;SPAN style="color: black; line-height: 107%; font-family: 'Calibri','sans-serif'; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: SimSun; mso-fareast-theme-font: minor-fareast; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: Arial; mso-bidi-theme-font: minor-bidi; mso-themecolor: text1; mso-ansi-language: ES-BO; mso-fareast-language: JA; mso-bidi-language: AR-SA;"&gt;UNLIMITED TABLESPACE&lt;/SPAN&gt; to SDE on migration, but after the migration what quota do the SDE need?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm using Oracle 11.2.0.3 and ArcGIS 10.1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jul 2015 13:33:53 GMT</pubDate>
      <guid>https://community.esri.com/t5/geodatabase-questions/tablespace-size/m-p/858516#M5607</guid>
      <dc:creator>DavidSuarez2</dc:creator>
      <dc:date>2015-07-15T13:33:53Z</dc:date>
    </item>
    <item>
      <title>Re: Tablespace size</title>
      <link>https://community.esri.com/t5/geodatabase-questions/tablespace-size/m-p/858517#M5608</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What is the problem you are having with tablespace size?&amp;nbsp; Do you see a particular error?&amp;nbsp; If so, please share it with us.&amp;nbsp; &lt;/P&gt;&lt;P&gt;UNLIMITED TABLESPACE to SDE is a grant that is given to the SDE admin for geodatabase creation and upgrades just to ensure there is enough space.&amp;nbsp; It can be revoked after these operations.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jul 2015 14:03:49 GMT</pubDate>
      <guid>https://community.esri.com/t5/geodatabase-questions/tablespace-size/m-p/858517#M5608</guid>
      <dc:creator>TinaMorgan1</dc:creator>
      <dc:date>2015-07-15T14:03:49Z</dc:date>
    </item>
    <item>
      <title>Re: Tablespace size</title>
      <link>https://community.esri.com/t5/geodatabase-questions/tablespace-size/m-p/858518#M5609</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You should not ever have any spatial data in the SDE tablespace (it should be exclusively reserved for geodatabase metadata tables), so the quota on SDE should not in any way be impacted by geometry storage migration.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would not recommend &lt;EM&gt;in-situ&lt;/EM&gt; geometry migration (the process does significant damage to the base table [through fragmentation and high water mark creep]).&amp;nbsp; If you need to recreate the tables for performance reasons, then you might as well create new tablespaces to manage them as neatly as possible (provide for storage increase by setting a quota 50% larger than the previous usage, then reducing it when the smoke clears.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.esri.com/thread/162136"&gt;Another recent thread&lt;/A&gt; discussed this same issue, so I recommend you review the spatial defragmentation recommendation as well.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jul 2015 17:28:00 GMT</pubDate>
      <guid>https://community.esri.com/t5/geodatabase-questions/tablespace-size/m-p/858518#M5609</guid>
      <dc:creator>VinceAngelo</dc:creator>
      <dc:date>2015-07-15T17:28:00Z</dc:date>
    </item>
  </channel>
</rss>

