How to write to a sql error to windows server event viewer

Over the last few versions SQL Server has improved greatly on writing sql server  error messages . A good example is writing  to both SQL Server Error Log and the windows server event viewer.

There are a number of benefits in writing a SQL Server error to the windows event viewer.

1. Centralising error messages to the one source makes it more efficient for a monitoring application. It is possible for the monitoing package to parse the Windows event viewer and extract all alerting situations from the one source. This minimises the access footprint on the server . There is no requirement for the monitoring applications to log into SQL Server.
2. The DBA may want to manage alert messaging to different groups of administrators. For example , windows \ OS bases alerts could go to Windows Event Viewer and SQL Server Errors to the SQL Server Logs.

To write a message to windows event viewer is impolemented by using the procedure : xp_logevent

An example is :

EXEC xp_logevent 60000, 'A message from MSSQL$TEST', informational

Which would generate an Windows Event Viewer entry in the Application Logs

Error: 60000 Severity: 10 State: 1 A message from MSSQL$TEST

Note: db_owner or sysadmin is required

Related articles

Troubleshoot SQL Security Error Ring Buffer Recorded - System Health

Execute permission was denied on the object

How to find the SQL Server service pack is installed

How to troubleshoot Error 2601 Cannot insert duplicate key row in object '%.*ls' with unique index '%.*ls'. The duplicate key value is %ls.