You administer a Microsoft SQL Server 2012 database.
Users report that an application that accesses the database displays an error, but the error
does not provide meaningful information. No entries are found in the SQL Server log or
Windows event logs related to the error.
You need to identify the root cause of the issue by retrieving the error message.
What should you do?
A.
Create an Extended Events session by using the sqlserver.error_reported event.
B.
Create a SQL Profiler session to capture all ErrorLog and EventLog events.
C.
Flag all stored procedures for recompilation by using sp_recompile.
D.
Execute sp_who.
Explanation:
http://msdn.microsoft.com/en-us/library/bb630282.aspx
Event sqlserver.error_reported: This event gets fired every time that an error happens in the server
@see http://www.mssqltips.com/sqlservertip/2155/getting-started-with-extended-events-in-sql-server-2008/
0
0
A
0
0
Correct answer : A
Explanation : SQL Server Profiler and Extended Events are both ways to trace the error message.
In Profiler the task will be difficult, because Profiler trace any event occuring in the server, in other hand Extended Events will trace only sqlserver.error_reported events which makes Extended Events more accurate than Profiler
0
0