You also use the Semantic Logging Application Block for the same reasons: collecting diagnostic information from your application, debugging, and troubleshooting.

The answer why you might want to use the Semantic Logging Application Block lies with how the application writes messages to the logs.

SQL Heroes 2008 Contest Winners These awesome contributors took home a Windows Home Server (HP Media Smart ex470) from SQL PASS 2008 for their great contributions to SQL Server community projects.

We're proud to have such smart folks in our community!!

The key advantages of the out-of-process approach are that it makes logging more resilient to application crashes and facilitates correlating log data from multiple sources.

If your application crashes, any log messages are likely to be already buffered in the ETW infrastructure and so will be processed and saved.

Note: This is one monolithic set of all Microsoft SQL Server product samples (except for the sample databases, due to size constraints) and does NOT include any community projects.

If you are interested in a specific subject area, links to download individual technology-focused samples are below.

SQL Server 2005 product samples can still be downloaded and separately Adventure Works for SQL Server 2005.

Code Plex is the project hosting site for Microsoft SQL Server Samples and Community Projects.

In the future, you can easily migrate to a complete ETW-based solution without modifying your application code: you continue to use the same custom Event Source class, but use ETW tooling to capture and process your log messages instead of using the Semantic Logging Application Block event listeners.

You can think of the Semantic Logging Application Block as a stepping stone from a traditional logging approach (such as that taken by the Logging Application Block), to a modern, semantic approach as provided by ETW.

Why do you need another logging block when the Logging Application Block already has a comprehensive set of features?