Icon View Incident Report

Serious Serious
Reported By: Wolfgang Klein [AESA GmbH]
Reported On: 1/24/2020
For: Version 2.31 Build 7
# 4774 Queries Not Using Available Indexes for ORDER BY Columns that Match View Correlation Names

There seems to be a optimization issue when using views and "select order by".

A existing index is not used for sorting when the "order by" expression accesses a field from the view. It is working if the "order-by" expression uses the corresponding field from the underlying table.

All queries where conducted with "Request Sensitive Result Set".

Query:

SELECT ALL
"ProbenIDNr" AS "ProbenIDNr",
"PrüfauftragNr" AS "PrüfauftragNr"
FROM "VProben-DE"
ORDER BY "PrüfauftragNr"

View:

CREATE VIEW "VProben-DE" AS
SELECT "RecNo",
"PANR",
"AGNR",
"PANR" as "PrüfauftragNr",
"AGNR" as "ArbeitsgangNr",
"IDNR" as "ProbenIDNr",
"STATUS" as "Status",
"SUBSTATUS" as "SubStatus",
"FEHLER" as "Fehler",
"ERFN" as "ErfaßtName",
"ERF" as "ErfaßtDatumZeit",
"KBNR" as "ProbenNr",
"ANWENDWERT" as "Anwenderwert",
"FLAGAR" as "FlagArchivieren",
"ARCHI" as "ArchiviertDatumZeit",
"ARCHIN" as "ArchiviertName",
"AKIDNR" as "AktuellPBIDNr",
"AKTUELL" as "AktuellDatumZeit",
"AKTUELLN" as "AktuellName",
"ORIDNR" as "OriginalPBIDNr",
"ORIGINAL" as "OriginalDatumZeit",
"ORIGINALN" as "OriginalName",
"PPNR" as "PrüfplanNr",
"PPVERSION" as "PrüfplanVersion",
"DATUMZEIT" as "DatumZeit",
"NAME" as "Name"
FROM "IWProben"



Resolution Resolution
Fixed Problem on 5/5/2020 in version 2.31 build 13


Products Affected 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

Image