<?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: Significant performance issues after simple join in Geoprocessing Questions</title>
    <link>https://community.esri.com/t5/geoprocessing-questions/significant-performance-issues-after-simple-join/m-p/603695#M20044</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;CORRECTION:&amp;nbsp; The feature class (layer) has the 8,700 records.&amp;nbsp; The join table has 58 records, all of which should match&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 07 Aug 2017 13:26:09 GMT</pubDate>
    <dc:creator>Anonymous User</dc:creator>
    <dc:date>2017-08-07T13:26:09Z</dc:date>
    <item>
      <title>Significant performance issues after simple join</title>
      <link>https://community.esri.com/t5/geoprocessing-questions/significant-performance-issues-after-simple-join/m-p/603694#M20043</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;10.5 Desktop.&amp;nbsp; Significant performance issue after join; cursor just spins when attempting to view the attribute table.&amp;nbsp; Feature class has 58 records and join table has 8,711 records.&amp;nbsp; Join to keep only matching.&amp;nbsp; Validate shows OK and the number of matches is 58 (as expected).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have tested with join table in Excel 2010 and as .csv file.&amp;nbsp; Have attempted to export the resultant data file to a GDB feature class, but cursor just spins.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sometimes throws an error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Join is run from the Desktop window (i.e. not Python).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Apologies if posted to wrong forum.&amp;nbsp; Don't post often.&amp;nbsp; Address correction requested.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Aug 2017 12:49:03 GMT</pubDate>
      <guid>https://community.esri.com/t5/geoprocessing-questions/significant-performance-issues-after-simple-join/m-p/603694#M20043</guid>
      <dc:creator>Anonymous User</dc:creator>
      <dc:date>2017-08-07T12:49:03Z</dc:date>
    </item>
    <item>
      <title>Re: Significant performance issues after simple join</title>
      <link>https://community.esri.com/t5/geoprocessing-questions/significant-performance-issues-after-simple-join/m-p/603695#M20044</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;CORRECTION:&amp;nbsp; The feature class (layer) has the 8,700 records.&amp;nbsp; The join table has 58 records, all of which should match&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Aug 2017 13:26:09 GMT</pubDate>
      <guid>https://community.esri.com/t5/geoprocessing-questions/significant-performance-issues-after-simple-join/m-p/603695#M20044</guid>
      <dc:creator>Anonymous User</dc:creator>
      <dc:date>2017-08-07T13:26:09Z</dc:date>
    </item>
  </channel>
</rss>

