Query Execution Plan

Hi all
Can anyone provide me general description or link about the details shows in
query execution plan.
How to use it to decide more better performance.
Which steps in exectuion plan are not good and need to improve. Is there any
general description on it?
ThanksSee if this helps
--
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"AM" <anonymous@.developersdex.com> wrote in message
news:eLldf1dSFHA.3720@.TK2MSFTNGP10.phx.gbl...
> Hi all
> Can anyone provide me general description or link about the details shows
in
> query execution plan.
> How to use it to decide more better performance.
> Which steps in exectuion plan are not good and need to improve. Is there
any
> general description on it?
>
> Thanks
>
>|||AM wrote:
> Hi all
> Can anyone provide me general description or link about the details
> shows in query execution plan.
> How to use it to decide more better performance.
> Which steps in exectuion plan are not good and need to improve. Is
> there any general description on it?
>
> Thanks
BOL has some basic information. You might try reading Kalen Delaney's
book "Inside SQL Server 2000" or "SQL Server 2000 Performance Tuning".
Or check out SQLServerPerformance.com.
In general, "scan" operations are bad and mean an index is unavailable
or cannot be utilized for best performance.
- Table Scan - on a table without a clustered index (a heap)
- Clustered Index Scan - on a table with a clustered index (could be a
partial scan)
- Index Scan - just means an index is scanned (could be a partial scan)
"Seek" operations are good and mean an index is used.
- Index Seek
"Bookmark Lookup" operations are necessary for many queries that use
non-clustered indexes, but can add about 50% overhead to using the
index. The lookup is used to access column values in the table that are
not in the index. You can sometimes avoid bookmark lookup ops with a
well-designed clustered index or covering indexes.
"Sort" operations are... sometimes bad, sometimes necessary, but always
add overhead. If your sort ops are there because of an ORDER BY in the
query, remove it. Few applications require sorted data come back from
SQL Server and many developers leave them in because sorted results are
easier to debug during development.
David Gugick
Imceda Software
www.imceda.com|||Thanks all
"Narayana Vyas Kondreddi" <answer_me@.hotmail.com> wrote in message
news:%23GGILfeSFHA.3664@.TK2MSFTNGP15.phx.gbl...
> See if this helps
> --
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "AM" <anonymous@.developersdex.com> wrote in message
> news:eLldf1dSFHA.3720@.TK2MSFTNGP10.phx.gbl...
> > Hi all
> > Can anyone provide me general description or link about the details
shows
> in
> > query execution plan.
> > How to use it to decide more better performance.
> > Which steps in exectuion plan are not good and need to improve. Is there
> any
> > general description on it?
> >
> >
> > Thanks
> >
> >
> >
> >
>