| title | View the Windows application log (Windows) | Microsoft Docs | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| ms.custom | |||||||||
| ms.date | 02/01/2017 | ||||||||
| ms.prod | sql | ||||||||
| ms.reviewer | |||||||||
| ms.technology | performance | ||||||||
| ms.topic | conceptual | ||||||||
| helpviewer_keywords |
|
||||||||
| ms.assetid | 168a6c6e-12df-46a9-9904-55d63ca8fe14 | ||||||||
| author | julieMSFT | ||||||||
| ms.author | jrasnick |
[!INCLUDEappliesto-ss-xxxx-xxxx-xxx-md] When [!INCLUDEssNoVersion] is configured to use the Windows application log, each [!INCLUDEssNoVersion] session writes new events to that log. Unlike the [!INCLUDEssNoVersion] error log, a new application log is not created each time you start an instance of [!INCLUDEssNoVersion].
-
On the Search bar, type Event Viewer, and then select the Event Viewer desktop app.
-
In Event Viewer, open the Applications and Services Logs.
-
[!INCLUDEssNoVersion] events are identified by the entry MSSQLSERVER (named instances are identified with MSSQL$<instance_name>) in the Source column. SQL Server Agent events are identified by the entry SQLSERVERAGENT (for named instances of [!INCLUDEssNoVersion], [!INCLUDEssNoVersion] Agent events are identified with SQLAgent$<instance_name>). Microsoft Search service events are identified by the entry Microsoft Search.
-
To view the log of a different computer, right-click Event Viewer (local). Select Connect to another computer, and fill in the fields to complete the Select Computer dialog box.
-
Optionally, to display only [!INCLUDEssNoVersion] events, on the View menu, select Filter. In the Event source list, select MSSQLSERVER. To view only [!INCLUDEssNoVersion] Agent events, instead select SQLSERVERAGENT in the Event source list.
-
To view more information about an event, double-click the event.
View the SQL Server error log (SQL Server Management Studio)