You are experiencing performance issues with the database server.
You need to evaluate schema locking issues, plan cache memory pressure points, and backup I/O problems.
What should you create?

A.
a System Monitor report

B.
a sys.dm_exec_query_stats dynamic management view query

C.
a sys.dm_exec_session_wait_stats dynamicmanagement view query

D.
an Activity Monitor session in Microsoft SQL Management Studio.

Explanation:
sys.dm_exec_session_wait_stats returns information about all the waits encountered by threads that executed
for each session. You can use this view to diagnose performance issues with the SQL Server session and also
with specific queries and batches.
Note: SQL Server wait stats are, at their highest conceptual level, grouped into two broad categories: signal
waits and resource waits. A signal wait is accumulated by processes running on SQL Server which are waiting
for a CPU to become available (so called because the process has “signaled” that it is ready for processing). A
resource wait is accumulated by processes running on SQL Server which are waiting fora specific resource to
become available, such as waiting for the release of a lock on a specific record.