Fernando,

<<
EDB only uses the first column of any index for optimization.
This is more or less the same Roy as said but if you don't believe us,
you can always read the manual:
>>

Thank you for the information. I didn't want to affront TeamElevate, but:

1. If I had found the information in the manual I wouldn't have asked the question here.
2. It's not a question of believe or not to believe on my part. It's a question of knowing
or guessing.

So no need to be that sensible.

Regards Uli

Uli,

<< So no need to be that sensible. >>

I'm not going to take sides in this discussion. But as a dictionary builder,
I just have to clarify "sensible" for the monolingual English speakers...

Sensible (FR), sensibile (IT) or sensibel (DE): in most European languages
this will mean "sensitive", "hyper-sensitive", "over-reactive" or "touchy".

In British or US English, "sensible" means rational or reasonable.

This word can lead to many, many misunderstandings.

Regards,
Dan

Dan,

<<This word can lead to many, many misunderstandings. >>

You are right. I was not my intention to  annoy someone.

Regards to all (especially to TeamElevate )

Uli

Roy,

> Sorry I'm not helpful. Try searching the elevatedb ng's for the word
> compound and you'll see what I'm basing my opinion on.
>

My apologizes. I always appreciate your help.
Obviously I had a bad day trying to speed up a slow and complex stored
procedure without success.

Best regards Uli Becker

Dan, Uli

> Sensible (FR), sensibile (IT) or sensibel (DE): in most European languages
> this will mean "sensitive", "hyper-sensitive", "over-reactive" or "touchy".

Sensivel (PT) has the same meaning, so no misunderstandings here.
And Uli, don't worry - I don't .

--
Fernando Dias
[Team Elevate]

Dan,

<< I'm not going to take sides in this discussion. But as a dictionary
builder, I just have to clarify "sensible" for the monolingual English
speakers... >>

Wow, I never knew that.  That could really lead to some misunderstandings.


--
Tim Young
Elevate Software
www.elevatesoft.com

Uli,

Just one clarification:

"As things stand ElevateDB will only use the Name part of the index and do a
brute force scan for the second item"

The "brute force" scan isn't really "brute force" because the EDB is smart
enough to do the index scan first and then only scan the rows that match the
first index scan in the second part.  So, the general idea is to have the
first condition be restrictive enough to cut down on the number of rows
being scanned for any other condition, and that should be very efficient.

--
Tim Young
Elevate Software
www.elevatesoft.com

Uli


Don't worry about offending me - its very difficult to do. The only reason I haven't been posting for the last few days is I haven't been here.

Roy Lambert

Uli


See above (or below, I'm not sure of the direction) post

Roy Lambert

Roy,

> Don't worry about offending me - its very difficult to do. The only reason
> I haven't been posting for the last few days is I haven't been here.

Thank you