The object, output list and seek predicates of execution plan

Dear all,

from the execution plan some times we see this :

predicates
what is the object, output list and seek predicates means ? normally what should we do on this ?
LVL 1
marrowyungSenior Technical architecture (Data)Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

lcohanDatabase AnalystCommented:
<<
object = it usually the actual database table
output list = is the SELECT column list
and seek predicates = your WHERE and/OR JOIN clauses.
>>

<< what should we do on this>> - nothing if the plan looks like in your screen shot as Non-clustered Index-seek is ideal case in any query plan for a SELECT .
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
marrowyungSenior Technical architecture (Data)Author Commented:
"object = it usually the actual database table " 

so this just the table select by the queries ?

"as Non-clustered Index-seek is ideal case in any query plan for a SELECT . "

you mean if we see any index seeks instead of index scan / table scan, already perfect?

what I also means how can we make use of this when tuning our query?
0
marrowyungSenior Technical architecture (Data)Author Commented:
any comment ?
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Vitor MontalvãoMSSQL Senior EngineerCommented:
An Index Seek should be one of the more performant operations that you'ld like to see in the Execution Plan.
In your case it's saying that is using the index IX_ProductId_TransactionDate for the following WHERE clause:
bigTransactionHistory.ProductID >= 0 AND bigTransactionHistory.ProductID <= 1
0
marrowyungSenior Technical architecture (Data)Author Commented:
"An Index Seek should be one of the more performant operations that you'ld like to see in the Execution Plan."

yeah, because it find the right index, right? index scan also not good as the table do not have a good index to use and SQL server still scan that index as the cost is cheaper than table scan.

but here what I tried to learn more is the predicates, I never make use of this before and may I know how can I make use of this to find tune my queries?

it seems for our information only and not much to do on tuning ?
0
Vitor MontalvãoMSSQL Senior EngineerCommented:
but here what I tried to learn more is the predicates, I never make use of this before and may I know how can I make use of this to find tune my queries?
Predicate is one of your test condition is the search criteria (WHERE clause).
For example here you have 2 predicates:
bigTransactionHistory.ProductID >= 0 AND bigTransactionHistory.ProductID <= 1
but here only one: bigTransactionHistory.ProductID = 0
0
marrowyungSenior Technical architecture (Data)Author Commented:
yeah, tks.

but it seems there are nothing we can do by this but for information only ?
0
Vitor MontalvãoMSSQL Senior EngineerCommented:
All the information in an execution plan is for your reference only. There's no error or warnings because it only says how your query was executed. Depends on your sensibility if you need to change something or not.
I usually like to focus where my query spends more time (high costs) to try to tunning that part of the query.
0
marrowyungSenior Technical architecture (Data)Author Commented:
"All the information in an execution plan is for your reference only."

but from time to time demo on the web keep focusing on this and I am not sure if I can make use of them or not.

from you, it seems really not much use, right?
0
Vitor MontalvãoMSSQL Senior EngineerCommented:
I like to see Execution Plan for queries that has performance issues. For sure I'm not using it on every queries. Just for does ones that runs for long.
0
marrowyungSenior Technical architecture (Data)Author Commented:
"Just for does ones that runs for long. "

ok, this mean you will also read that, so what can it do for you? this is what I want to know. or it just use in any SQL video to show what SQL server is doing ?
0
Vitor MontalvãoMSSQL Senior EngineerCommented:
Ok, what I think is that you need to understand better the icons that appears in an Execution Plan. Even I don't know all and when sometimes appears something new for me I just Google it.
Here's a good start article for you.
0
marrowyungSenior Technical architecture (Data)Author Commented:
yeah, good article tks
0
marrowyungSenior Technical architecture (Data)Author Commented:
tks all
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.