SELECT
File.FileID,
FileDictionary."Name"
FROM File
INNER JOIN FileDictionary ON File.FileDictionaryID = FileDictionary.FileDictionaryID
WHERE ( NodeId=1228 ) AND (File.Deleted = false) AND (File.UserActivity = false)
ORDER BY FileDictionary."Name"

Table:

CREATE TABLE "FileDictionary"
(
"FileDictionaryID" INTEGER GENERATED BY DEFAULT AS IDENTITY (START WITH 0, INCREMENT BY 1),
"Name" VARCHAR(256) COLLATE "UNI_CI",
"Version" VARCHAR(256) COLLATE "UNI_CI",
"Size" BIGINT,
"CompanyDictionaryID" INTEGER,
"Description" VARCHAR(256) COLLATE "UNI_CI",
"ProductName" VARCHAR(256) COLLATE "UNI_CI",
"OriginalFileName" VARCHAR(256) COLLATE "UNI_CI",
"Icon" BLOB
)
VERSION 2
UNENCRYPTED
INDEX PAGE SIZE 5288
BLOB BLOCK SIZE 2256
PUBLISH BLOCK SIZE 512
PUBLISH COMPRESSION 0
MAX ROW BUFFER SIZE 32768
MAX INDEX BUFFER SIZE 65536
MAX BLOB BUFFER SIZE 32768
MAX PUBLISH BUFFER SIZE 32768

---

 Comments

---

The problem was caused by ElevateDB not properly handling index page overflows with large index key sizes.

---

 Resolution

---

Fixed Problem on 1/15/2010 in version 2.03 build 8

---

 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 VCL Client-Server
ElevateDB VCL Client-Server with Source
ElevateDB VCL Standard
ElevateDB VCL Standard with Source
ElevateDB VCL Trial