70-457 · Question #173
You administer a Microsoft SQL Server 2012 server. One of the databases on the server supports a highly active OLTP application. Users report abnormally long wait times when they submit data into…
The correct answer is A. use SQL Profiler to trace all queries that are processing on the server. Trace 1222 is used for deadlocks. To take slow queries better to use Profile! --\Burgos Verified the SQL Profiler and DBCC answers as correct. However, while Profiler will show this information, the best practice with Profiler is to use it short-term. The question specifically…
Question
You administer a Microsoft SQL Server 2012 server. One of the databases on the server supports a highly active OLTP application. Users report abnormally long wait times when they submit data into the application. You need to identify which queries are taking longer than 1 second to run over an extended period of time. What should you do?
Options
- Ause SQL Profiler to trace all queries that are processing on the server.
- BUse sp_configure to set a value for blocked process threshold.
- CRun the sp_who command from a query window.
- DRun the DBCC TRACEON 1222 command from a query window and review the SQL Server event log.
How the community answered
(46 responses)- A78% (36)
- B2% (1)
- C13% (6)
- D7% (3)
Explanation
Trace 1222 is used for deadlocks. To take slow queries better to use Profile! --\Burgos Verified the SQL Profiler and DBCC answers as correct. However, while Profiler will show this information, the best practice with Profiler is to use it short-term. The question specifically states "over an extended period of time". That means Profiler wouldn't be the best tool for this scenario. Therefore, DBCC would be the best answer.
Topics
Community Discussion
No community discussion yet for this question.