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 Performance statistics 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 Soft Warnings in th

e Errors and Warnings event category.

D. Create one Extended Events session with the sqlserver.error_reported event added.

Explanation:

The Performance Statistics event class can be used to monitor the performance of queries, stored procedures,

and triggers that are executing. Each of the six event subclasses indicates an event in the lifetime of queries, stored procedures, and triggers within the system. Using the combination of these event subclasses and the associated sys.dm_exec_query_stats,

sys.dm_exec_procedure_stats and sys.dm_exec_trigger_stats dynamic management views, you can reconstitute the performance history of any given query, stored procedure, or trigger.

References: https://docs.microsoft.com/en-us/sql/relational-databases/event-

classes/performance-statistics-event-class?view=sql-server-2017