View Incident Report

Serious

Reported By: Terry Swiers
Reported On: 8/1/2017
For: Version 2.26 Build 2

# 4560 Queries Generating Sensitive Results Using Row Scans When They Shouldn't

I'm seeing a marked performance degradation between 2.26 and earlier versions of EDB. It appears that 2.26 prefers doing row scans rather than index scans.

A very simplified version of the table and query that I'm using is included below.

In EDB 2.24b3, the result set is returned almost immediately, but 2.26b takes 22 seconds as it's reading through the whole table.

Table:

CREATE TABLE "code"
(
"StockCode" VARCHAR(60) COLLATE "UNI" DESCRIPTION 'Unique stock code (SKU)',
"WhseOnHandOutOfDate" BOOLEAN DEFAULT False,
CONSTRAINT "PrimaryKey" PRIMARY KEY ("StockCode")
)
CREATE INDEX "WhseOnHandOutOfDate" ON "code" ("WhseOnHandOutOfDate")

Query:

select stockcode from code where WhseOnHandOutOfDate = False

Comments

This was a bug caused by the inclusion of the JOININDEXTHRESHHOLD features in 2.26.

Resolution

Fixed Problem on 8/2/2017 in version 2.26 build 3

Products Affected

ElevateDB Additional Software and Utilities
ElevateDB DAC Client-Server
ElevateDB DAC Client-Server with Source
ElevateDB DAC Standard
ElevateDB DAC Standard with Source
ElevateDB DAC Trial
ElevateDB LCL Standard with Source
ElevateDB PHP Standard
ElevateDB PHP Standard with Source
ElevateDB PHP Trial
ElevateDB VCL Client-Server
ElevateDB VCL Client-Server with Source
ElevateDB VCL Standard
ElevateDB VCL Standard with Source
ElevateDB VCL Trial

More Support Options

Search Incident Reports

Support Forums

Frequently Asked Questions

Technical Bulletins

Technical Articles

Product Manuals

Roadmap