<?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>idea Push down operations to spatial databases in Data Management Ideas</title>
    <link>https://community.esri.com/t5/data-management-ideas/push-down-operations-to-spatial-databases/idi-p/961739</link>
    <description>&lt;P&gt;When the geometries are accessed directly from a spatial database then ArcGIS should automatically general the according SQL using appropriate SQL consctucts and SQL/MM functions in the database. A good example here is the spatial join that should be broken down to happen in database whenever possible, e.g. usong ST_INTERSECT or similar spatial join operators of the database. Today the user has to manually type up the SQL query in a query layer to leverage the potentials of spatial databases with ArcGIS.&lt;/P&gt;&lt;!--  content transformation source ID: 087E0000000Cv45  --&gt;</description>
    <pubDate>Mon, 29 Aug 2022 21:57:51 GMT</pubDate>
    <dc:creator>TorstenSteinbach</dc:creator>
    <dc:date>2022-08-29T21:57:51Z</dc:date>
    <item>
      <title>Push down operations to spatial databases</title>
      <link>https://community.esri.com/t5/data-management-ideas/push-down-operations-to-spatial-databases/idi-p/961739</link>
      <description>&lt;P&gt;When the geometries are accessed directly from a spatial database then ArcGIS should automatically general the according SQL using appropriate SQL consctucts and SQL/MM functions in the database. A good example here is the spatial join that should be broken down to happen in database whenever possible, e.g. usong ST_INTERSECT or similar spatial join operators of the database. Today the user has to manually type up the SQL query in a query layer to leverage the potentials of spatial databases with ArcGIS.&lt;/P&gt;&lt;!--  content transformation source ID: 087E0000000Cv45  --&gt;</description>
      <pubDate>Mon, 29 Aug 2022 21:57:51 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-ideas/push-down-operations-to-spatial-databases/idi-p/961739</guid>
      <dc:creator>TorstenSteinbach</dc:creator>
      <dc:date>2022-08-29T21:57:51Z</dc:date>
    </item>
    <item>
      <title>Re: Push down operations to spatial databases</title>
      <link>https://community.esri.com/t5/data-management-ideas/push-down-operations-to-spatial-databases/idc-p/961740#M1134</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Down vote explained:&amp;nbsp; When doing a spatial join in Arc, using data from a SQL Geography or Geometry table, the join occurs within the application with little to no performance cost. Pushing that same join into a ST_INTERSECT&amp;nbsp;statement, especially when you're doing a join from many features to many features, would kill the database, in fact, you may be waiting for many days for the result to return. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Feb 2018 17:56:40 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-ideas/push-down-operations-to-spatial-databases/idc-p/961740#M1134</guid>
      <dc:creator>ThomasColson</dc:creator>
      <dc:date>2018-02-21T17:56:40Z</dc:date>
    </item>
  </channel>
</rss>

