performance problem

Hello there
I have table with at least 30,000,000 records
When i do simple select with 3 records who are indexed i get 90% on bookmark
lookup in the execution plan
what can cause it?have you got these indexes as non-cluster and besides of that, living in
another filegroup?
--
Please post DDL, DCL and DML statements as well as any error message in
order to understand better your request. It''s hard to provide information
without seeing the code. location: Alicante (ES)
"Roy Goldhammer" wrote:

> Hello there
> I have table with at least 30,000,000 records
> When i do simple select with 3 records who are indexed i get 90% on bookma
rk
> lookup in the execution plan
> what can cause it?
>
>|||> When i do simple select with 3 records who are indexed i get 90% on bookmarkd">
> lookup in the execution plan
When you say "records" I assume you mean "columns". A bookmark lookup may be
the best option for the optimizer if the index scans might take longer.
Are the statistics up to date? What's the query? Where are the indexes? What
kind of indexes are they?
ML
http://milambda.blogspot.com/|||Roy,
That seems right. And I guess the other 10% is caused by the index s.
All steps in the query plan will add up to 100%, even if the entire
query runs in a few millisecond. So the 90% is just the step cost in
relation to the total cost.
Is there anything you are worried about? The entire query probably takes
less than 20 logical reads and just a few milliseconds to run...
Gert-Jan
Roy Goldhammer wrote:
> Hello there
> I have table with at least 30,000,000 records
> When i do simple select with 3 records who are indexed i get 90% on bookma
rk
> lookup in the execution plan
> what can cause it?