Skip to content

Latest commit

 

History

History
45 lines (39 loc) · 3.42 KB

File metadata and controls

45 lines (39 loc) · 3.42 KB
title Monitoring the Error Logs
ms.custom seo-lt-2019
ms.date 03/14/2017
ms.prod sql
ms.prod_service sql-tools
ms.reviewer
ms.technology configuration
ms.topic conceptual
helpviewer_keywords
logs [SQL Server]
database performance [SQL Server], errors
Windows application logs [SQL Server]
monitoring performance [SQL Server], errors
server performance [SQL Server], errors
comparing error and application log output
errors [SQL Server], logs
tuning databases [SQL Server], errors
database monitoring [SQL Server], errors
SQL Server error log
logs [SQL Server], SQL Server error logs
error logs [SQL Server]
logs [SQL Server], Windows application logs
ms.assetid e250336b-0695-44f6-a42f-23222f94e377
author markingmyname
ms.author maghan
monikerRange >=sql-server-2016||=sqlallproducts-allversions

Monitoring the Error Logs

[!INCLUDEappliesto-ss-xxxx-xxxx-xxx-md-winonly] [!INCLUDEssNoVersion] logs certain system events and user-defined events to the [!INCLUDEssNoVersion] error log and the [!INCLUDEmsCoName] Windows application log. Both logs automatically timestamp all recorded events. Use the information in the [!INCLUDEssNoVersion] error log to troubleshoot problems related to [!INCLUDEssNoVersion].

The Windows application log provides an overall picture of events that occur on the Windows operating system, as well as events in [!INCLUDEssNoVersion] and [!INCLUDEssNoVersion] Agent. Use the Windows Event Viewer to view the Windows application log and to filter the information. For example, you can filter events, such as information, warning, error, success audit, and failure audit.

Comparing Error and Application Log Output

You can use both the [!INCLUDEssNoVersion] error log and the Windows application log to identify the cause of problems. For example, while monitoring the [!INCLUDEssNoVersion] error log, you may encounter error messages that do not contain cause information. By comparing the dates and times for events between these logs, you can narrow the list of probable causes. The [!INCLUDEssManStudioFull] Log File Viewer lets you integrate [!INCLUDEssNoVersion], [!INCLUDEssNoVersion] Agent, and the Windows logs into a single list, making it easy to understand related server events and [!INCLUDEssNoVersion] events. For more information, see the topic "Log File Viewer" in SQL Server Books Online.

In This Section

Topic Description
Viewing the SQL Server Error Log Contains information about the [!INCLUDEssNoVersion] error log and how to view it.
Viewing the Windows Application Log Contains information about the Windows application log and how to view it.