You use Microsoft SQL Server Profile to evaluate a query named Query1. The Profiler report indicates the following issues:
At
each level of the query plan, a low total number of rows are processed.
The query uses many operations. This results in a high overall cost for the query.
You need to identify the information that will be useful for the optimizer.
What should you do?
A.
Start a SQL Server Profiler trace for the event class Auto Stats in the Performance event category.
B. Create one Extended Events session with the sqlserver.missing_column_statistics event added.
C. Start a SQL Server Profiler trace for the event class So
ft Warnings in the Errors and Warnings event category.
D. Create one Extended Events session with the sqlserver.missing_join_predicate event added.
Explanation:
The Missing JoinPredicate event class indicates that a query is being executed that
has no join predicate. This could result in a long-running query.
D
2
4
B
7
0
I think the proposed answer is wrong.
Missing join predicate indicates that a query is being executed that has no join predicate. No benefit for the optimizer
https://docs.microsoft.com/en-us/sql/relational-databases/event-classes/missing-join-predicate-event-class?view=sql-server-ver15
Correct Answer is B
The Missing Column Statistics event class indicates that column statistics that could have been useful for the optimizer are not available
https://docs.microsoft.com/en-us/sql/relational-databases/event-classes/missing-column-statistics-event-class?view=sql-server-ver15
9
0