>>>How would you explain the fact I got 2 Index seeks with your test code and my addition of populating tables?
>>>
>>>>No, no matter if PRIMARY KEY index is CLUSTERED or not in both cases I have INDEX SEEK.
>>>>Thanks again Walter.
>>
>>I can't. :-)
>>I even can not explain why my friend has INDEX SEEK directly w/o running any code to populate data.
>
>Boris,
>
>Is there a performance problem or is it you just want to understand? SQL's cost based optimizer is complex and takes many things into account. Unless you're experiencing performance problems I would not worry too much about it.
>
>Walter,

I just want to understand WHY!

No, no problems for now. But soon it there will be.
The table in question now is very small about 9000 records, but because I never delete records in it will become bigger and bigger. That is why I want to undesrand.
There is no problem to add an autoincrement field and use it (whit all others) as PRIMARY KEY, but I just want to know :-)