<?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 Convert Geometry Storage from SDEBINARY to ST_GEOMETRY in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/convert-geometry-storage-from-sdebinary-to-st/m-p/510890#M29005</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello All,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I have the enterprise 9.3.1 SDE large GDB (around 1 TB ) where geometry is stored in SDEBINARY.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I am thinking to convert the geometry storage to ST_GEOMETRY and want to know your view and experience on that.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;1 . ST_GEOMETRY is default storage since 9.3 but is that recommended to convert from SDEBINARY to ST_GEOMETRY.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;2. Has that been done by someone and issue o approx time taken for the operation (although time taken depends on various factors)&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;3. Is there any concern or known issue?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;4. Will that fragment table?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;5. I am hoping that migration will also require adjustment in the code and entire custom code has to be tested.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Any view or any info which help to take the decision further will be appreciated. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Manoj&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 18 Feb 2014 06:12:49 GMT</pubDate>
    <dc:creator>ManojGarg</dc:creator>
    <dc:date>2014-02-18T06:12:49Z</dc:date>
    <item>
      <title>Convert Geometry Storage from SDEBINARY to ST_GEOMETRY</title>
      <link>https://community.esri.com/t5/data-management-questions/convert-geometry-storage-from-sdebinary-to-st/m-p/510890#M29005</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello All,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I have the enterprise 9.3.1 SDE large GDB (around 1 TB ) where geometry is stored in SDEBINARY.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I am thinking to convert the geometry storage to ST_GEOMETRY and want to know your view and experience on that.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;1 . ST_GEOMETRY is default storage since 9.3 but is that recommended to convert from SDEBINARY to ST_GEOMETRY.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;2. Has that been done by someone and issue o approx time taken for the operation (although time taken depends on various factors)&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;3. Is there any concern or known issue?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;4. Will that fragment table?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;5. I am hoping that migration will also require adjustment in the code and entire custom code has to be tested.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Any view or any info which help to take the decision further will be appreciated. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Manoj&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Feb 2014 06:12:49 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/convert-geometry-storage-from-sdebinary-to-st/m-p/510890#M29005</guid>
      <dc:creator>ManojGarg</dc:creator>
      <dc:date>2014-02-18T06:12:49Z</dc:date>
    </item>
    <item>
      <title>Re: Convert Geometry Storage from SDEBINARY to ST_GEOMETRY</title>
      <link>https://community.esri.com/t5/data-management-questions/convert-geometry-storage-from-sdebinary-to-st/m-p/510891#M29006</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;One of the driving force behind the above thought is sharing the data with non ESRI component with in the organization stream like big data etc.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Feb 2014 06:15:09 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/convert-geometry-storage-from-sdebinary-to-st/m-p/510891#M29006</guid>
      <dc:creator>ManojGarg</dc:creator>
      <dc:date>2014-02-18T06:15:09Z</dc:date>
    </item>
    <item>
      <title>Re: Convert Geometry Storage from SDEBINARY to ST_GEOMETRY</title>
      <link>https://community.esri.com/t5/data-management-questions/convert-geometry-storage-from-sdebinary-to-st/m-p/510892#M29007</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;A terabyte is trivial amount of raster data, but it's a lot of vector data.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ST_GEOMETRY has improved over the years -- There have been ten minor&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;releases since 9.3.1 SP2 (twelve since 9.3.1), but you don't have access&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;to any of them.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You're looking at using &lt;/SPAN&gt;&lt;SPAN style="font-style:italic;"&gt;retired&lt;/SPAN&gt;&lt;SPAN&gt; software for a significant change to your database.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I would not recommend this.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;To answer your questions:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;1) No&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;2) No way to even provide a glimmer (all dependent on missing information)&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;3) Tons of concerns&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;4) Absolutely&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;5) Why are you hoping that?&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, 18 Feb 2014 12:09:44 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/convert-geometry-storage-from-sdebinary-to-st/m-p/510892#M29007</guid>
      <dc:creator>VinceAngelo</dc:creator>
      <dc:date>2014-02-18T12:09:44Z</dc:date>
    </item>
    <item>
      <title>Re: Convert Geometry Storage from SDEBINARY to ST_GEOMETRY</title>
      <link>https://community.esri.com/t5/data-management-questions/convert-geometry-storage-from-sdebinary-to-st/m-p/510893#M29008</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;A terabyte is trivial amount of raster data, but it's a lot of vector data.&lt;BR /&gt; &lt;BR /&gt;ST_GEOMETRY has improved over the years -- There have been ten minor&lt;BR /&gt;releases since 9.3.1 SP2 (twelve since 9.3.1), but you don't have access&lt;BR /&gt;to any of them.&lt;BR /&gt;&lt;BR /&gt;You're looking at using &lt;SPAN style="font-style:italic;"&gt;retired&lt;/SPAN&gt; software for a significant change to your database.&lt;BR /&gt;I would not recommend this.&lt;BR /&gt;&lt;BR /&gt;To answer your questions:&lt;BR /&gt;1) No&lt;BR /&gt;2) No way to even provide a glimmer (all dependent on missing information)&lt;BR /&gt;3) Tons of concerns&lt;BR /&gt;4) Absolutely&lt;BR /&gt;5) Why are you hoping that?&lt;BR /&gt;&lt;BR /&gt;- V&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Vince, Thanks for response.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Its vector data with Geometric network and open versions.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I agree that 9.3.1 is retired but we have certain dependancy. Going to 10.2 will take almost 12-15 months minimum. You can say then 10.2 will be slightly outdated :). &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I am also exploring the option even if that is suggested or having mileage in converting to ST_GEOMETRY after upgrading to 10.2. &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;From your response I am getting glimpse that should be done.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks a lot.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Feb 2014 14:00:17 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/convert-geometry-storage-from-sdebinary-to-st/m-p/510893#M29008</guid>
      <dc:creator>ManojGarg</dc:creator>
      <dc:date>2014-02-19T14:00:17Z</dc:date>
    </item>
    <item>
      <title>Re: Convert Geometry Storage from SDEBINARY to ST_GEOMETRY</title>
      <link>https://community.esri.com/t5/data-management-questions/convert-geometry-storage-from-sdebinary-to-st/m-p/510894#M29009</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;my *personal* openion is that you should start migration form now before upgrading if possible.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 23 Feb 2014 10:02:45 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/convert-geometry-storage-from-sdebinary-to-st/m-p/510894#M29009</guid>
      <dc:creator>EmadAl-Mousa</dc:creator>
      <dc:date>2014-02-23T10:02:45Z</dc:date>
    </item>
  </channel>
</rss>

