The Windows Event Logs on any server can provide insight to potential and real problems. As a SQL Server Database

Administrator, it is important to have knowledge of problems that exist outside of SQL Server as well as inside of SQL

Server. At times hardware problems such as controller failures, may be logged in the Windows Event Logs prior to

SQL Server reading a page from the database that is corrupt.

There is no native method in SQL Server that can be used to monitor the System Event Logs. However, VBScript and

WMI can be used to read the System Event Logs in a SQL Agent Job through a Operating System(cmdExec) job step.

In SQL Server 2005 and 2008 it is also possible to use a WMI Data Reader in Integration Services as well as make use

of CLR to allow easy access to the System Event Logs.

http://www.codecomments.com/WSH/message462337.html