RE: CURSOR-Table Scan vs Index Scan -- MIDRANGE-L

Subject: RE: CURSOR-Table Scan vs Index Scan
From: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
Date: Fri, 29 Jun 2018 21:56:02 +0000
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

I took a stab at it and create a regular index. Run SQL Scripts used it and the execution time down was 8ms. Embedded SQL rejected the index for the same reason as before.

This may just be one of those things I just have to live with...

-----Original Message-----
From: Justin Taylor
Sent: Friday, June 29, 2018 4:26 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: CURSOR-Table Scan vs Index Scan

Any thoughts on an index, regular vs EVI?

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.