On Wed, Jan 18, 2012 at 12:29 PM, Dan Covill <dcov...@san.rr.com> wrote:
> I don't > see why an INDEX ON .... FOR .... wouldn't work Unless things changed since I left FoxPro,... An index created with a FOR clause is never used in Rushmore. SET FILTER can use Rushmore to optimize performance. An index on each column you are filtering with be optimal. You may also need an index on DELETED() but you MUST test with your data, on your hardware, as there are a lot of other factors that play into fully optimizing the performance. A fully Rushmore optimized express is not ALWAYS (but usually is) the fastest. This is old hat. Check the Hacker's Guide, or Tamar's SQL book. -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/CACW6n4ui0=yC+KWuYr_=g-63bnqg_iqlfykqbc0q1_l06+u...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
