davidathompson/serilog-sinks-mssqlserver

A Serilog sink that writes events to Microsoft SQL Server

Serilog.Sinks.MSSqlServer

A Serilog sink that writes events to Microsoft SQL Server. While a NoSql store allows for more flexibility to store the different kinds of properties, it sometimes is easier to use an already existing MS SQL server. This sink will write the logevent data to a table and can optionally also store the properties inside an Xml column so they can be queried.

Package - Serilog.Sinks.MSSqlServer | Platforms - .NET 4.5

You'll need to create a database and add a table like the one you can find in this Gist.

var log = new LoggerConfiguration()
    .WriteTo.MSSqlServer(connectionString: @"Server=...", tableName: "Logs")
    .CreateLogger();

Make sure to set up security in such a way that the sink can write to the log table. If you don't plan on using the properties, then you can disable the storage of them.

XML configuration

If you are configuring Serilog with the ReadFrom.AppSettings() XML configuration support, you can use:

<add key="serilog:using:MSSqlSever" value="Serilog.Sinks.MSSqlServer" />
<add key="serilog:write-to:MSSqlServer.connectionString" value="Server=..."/>
<add key="serilog:write-to:MSSqlServer.tableName" value="Logs"/>

Writing properties as columns

This feature will still use all of the default columns and provide additional columns for that can be logged to (be sure to create the extra columns via SQL script first). This gives the flexibility to use as many extra columns as needed.

var dataColumns = new[]
    {
        new DataColumn { DataType = typeof(string), ColumnName = "User" },
        new DataColumn { DataType = typeof(string), ColumnName = "Other" },
    };
    
var log = new LoggerConfiguration()
    .WriteTo.MSSqlServer(@"Server=...", "Logs", additionalDataColumns: dataColumns)
    .CreateLogger();

The log event properties User and Other will now be placed in the corresponding column upon logging. The property name must match a column name in your table.