topic Poor performance join on database VS file geodatabase in Developers Questions https://community.esri.com/t5/developers-questions/poor-performance-join-on-database-vs-file/m-p/195435#M1189 <HTML><HEAD></HEAD><BODY><P>Hi,</P><P></P><P>We have a feature class and a joined table by attribute.</P><P>Recently, we change the source of the joined table.</P><P>In the past, it was located in a geodatabase, now - in a file geodatabase.</P><P></P><P>The problem is a poor performance on Select by attribute by the field from the joined table.</P><P></P><P>Both joined fields are indexed. Searching field (<SPAN>Select by attribute)</SPAN> is indexed.</P><P>The only difference is that in the past the&nbsp;joined field in joined table was a primary key, now not (just indexed).</P><P></P><P>What could be a reason for the poor performance?</P></BODY></HTML> Mon, 17 Jul 2017 23:37:25 GMT MarkMindlin 2017-07-17T23:37:25Z Poor performance join on database VS file geodatabase https://community.esri.com/t5/developers-questions/poor-performance-join-on-database-vs-file/m-p/195435#M1189 <HTML><HEAD></HEAD><BODY><P>Hi,</P><P></P><P>We have a feature class and a joined table by attribute.</P><P>Recently, we change the source of the joined table.</P><P>In the past, it was located in a geodatabase, now - in a file geodatabase.</P><P></P><P>The problem is a poor performance on Select by attribute by the field from the joined table.</P><P></P><P>Both joined fields are indexed. Searching field (<SPAN>Select by attribute)</SPAN> is indexed.</P><P>The only difference is that in the past the&nbsp;joined field in joined table was a primary key, now not (just indexed).</P><P></P><P>What could be a reason for the poor performance?</P></BODY></HTML> Mon, 17 Jul 2017 23:37:25 GMT https://community.esri.com/t5/developers-questions/poor-performance-join-on-database-vs-file/m-p/195435#M1189 MarkMindlin 2017-07-17T23:37:25Z