Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 3 of 3 total
Thread Example of problem with index Case-Sensitive
Fri, Jul 25 2008 1:41 PMPermanent Link

Francisco Fernandez
Tim, Roy

After many tests i could have verified that the problem with performance with index
Case-Sensitive comes when i have triggers in the table that update another tables.

I have prepared an example for you where you can see it easily. In the code there are two
buttons where update four records of a table, one button with index Case-Sensitive and one
button with index Case-Insensitive. You can see that with the same code the manage with
index Case-Sensitive is more slowly than Case-Insensitive.

The project must be at a folder called C:\Example to run.

Thank you very much



Attachments: Example.rar
Fri, Jul 25 2008 2:10 PMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Francisco

Since the collation for the index and the collation for the column are different you need to give ElevateDB a hint that it should be looking at a case sensitive index.....

PREPARE stmt FROM 'SELECT * FROM Articulos WHERE CODIGO COLLATE ANSI =?

Roy Lambert
Sat, Jul 26 2008 4:37 AMPermanent Link

Francisco Fernandez
Roy

Great, i didn't know that was especify collation in trigger.

Thank you very much for all.
Image