<?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: st_geometry performance in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/st-geometry-performance/m-p/336412#M19122</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Adding more groups for better visibility. &lt;A href="https://community.esri.com/groups/geodatabase?sr=search&amp;amp;searchId=5f91017e-08f0-41c2-85a3-e78626b0c218&amp;amp;searchIndex=0"&gt;https://community.esri.com/groups/geodatabase?sr=search&amp;amp;searchId=5f91017e-08f0-41c2-85a3-e78626b0c218&amp;amp;searchIndex=0&lt;/A&gt;‌ &lt;A href="https://community.esri.com/community/gis/enterprise-gis?sr=search&amp;amp;searchId=dd891da0-22b3-4750-ad52-c1b796e05c85&amp;amp;searchIndex=0"&gt;https://community.esri.com/community/gis/enterprise-gis?sr=search&amp;amp;searchId=dd891da0-22b3-4750-ad52-c1b796e05c85&amp;amp;searchIndex=0&lt;/A&gt;‌&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 17 Feb 2017 17:47:35 GMT</pubDate>
    <dc:creator>George_Thompson</dc:creator>
    <dc:date>2017-02-17T17:47:35Z</dc:date>
    <item>
      <title>st_geometry performance</title>
      <link>https://community.esri.com/t5/data-management-questions/st-geometry-performance/m-p/336411#M19121</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are creating a materialized view from two tables via a dblink (all databases on the same server) that will process, initially, roughly 4.5 million records.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are adding a sde.st_geometry column which constructs a point from an X and Y column in one of the tables.&lt;/P&gt;&lt;P&gt;Currently to create 10,000 rows it takes an hour and a half.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sde.st_geometry ('point (' || w.SOURCELON || ' ' || w.SOURCELAT || ')', 4267 )&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is that expected performance?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Removing the line that creates the spatial column and the view will create in a couple of seconds. &amp;nbsp;So st_geometry is causing a huge performance bottle neck.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Oracle 11g&lt;/P&gt;&lt;P&gt;SDE 10.4.1&lt;/P&gt;&lt;P&gt;Oracle Linux 6.7&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Feb 2017 17:38:30 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/st-geometry-performance/m-p/336411#M19121</guid>
      <dc:creator>RobClark3</dc:creator>
      <dc:date>2017-02-17T17:38:30Z</dc:date>
    </item>
    <item>
      <title>Re: st_geometry performance</title>
      <link>https://community.esri.com/t5/data-management-questions/st-geometry-performance/m-p/336412#M19122</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Adding more groups for better visibility. &lt;A href="https://community.esri.com/groups/geodatabase?sr=search&amp;amp;searchId=5f91017e-08f0-41c2-85a3-e78626b0c218&amp;amp;searchIndex=0"&gt;https://community.esri.com/groups/geodatabase?sr=search&amp;amp;searchId=5f91017e-08f0-41c2-85a3-e78626b0c218&amp;amp;searchIndex=0&lt;/A&gt;‌ &lt;A href="https://community.esri.com/community/gis/enterprise-gis?sr=search&amp;amp;searchId=dd891da0-22b3-4750-ad52-c1b796e05c85&amp;amp;searchIndex=0"&gt;https://community.esri.com/community/gis/enterprise-gis?sr=search&amp;amp;searchId=dd891da0-22b3-4750-ad52-c1b796e05c85&amp;amp;searchIndex=0&lt;/A&gt;‌&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Feb 2017 17:47:35 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/st-geometry-performance/m-p/336412#M19122</guid>
      <dc:creator>George_Thompson</dc:creator>
      <dc:date>2017-02-17T17:47:35Z</dc:date>
    </item>
  </channel>
</rss>

