Mattias Lövström
Sep 3, 2010
visibility 6880
star star star star star
(0 votes)

LinqToSqlLogger as promised

As I promise in my past blog post Troubleshooting database tool – SqlClientLogger that I should deliver a logger for LinqToSql also. This is done and it is also located in the support tools area on EPiServer world.

The changes to LinqToSqlLogger and SqlClientLogger are

1) The installation – it has to be configured as a Http installation Module

2) It requires .Net 3.5 – of cause

3) The log4net logger is named “LinqToSqlLogger”

Known issues

Transactions doesn’t work (yet), this means that saving operations break the logger.

LinqToSqlLogger

This tool logs every LinqToSql call to the database done by the
application layer with a stack trace and a time it took to execute
the query. The benefits of using this tool is that it prints out
a stack trace so it’s easy to locate what code that generates the
database call. The logs are written to log4net and should appear in
the sites log file.

Requirements

.Net 3.5
Log4Net

Installation

Drop the assemblies in the packages bin/ folder to your sites bin/ folder
Add a reference to the initialization module handler for LinqToSqlLogger in the sites

web.config file
Example:
<configuration>
  …
  <system.webServer>
    …
      <add name="LinqToSqlLoggerModule" type="LinqToSqlLogger.InitializeModule, LinqToSqlLogger" />

Usage

When the LinqToSqlLogger is installed on the site it is going to send
log4net messages using the logger “LinqToSqlLogger”.

Log4Net logger levels

DEBUG – prints out database command, stack trace and execution time
INFO – prints out database command and execution time.
WARN – prints out database command, stack trace and execution time the execution time is over 500 ms

Sample of how to configure it in the file EPiServerLog.config (or where your log4net configuration is)
<log4net>
  ...
  <logger name="LinqToSqlLogger">
    <level value="DEBUG" />
  </logger>

Duration threshold can be set in the appSettings in the web.config file for the keys
SqlClientLoggerDurationFilterMs – a threshold for all logged database calls
SqlClientLoggerDurationWarnFilterMs - a threshold for trigger a warning message, the default is set to 500 ms

Download

LinqToSqlLogger.zip

Sep 03, 2010

Comments

Mattias Lövström
Mattias Lövström Oct 8, 2010 08:41 AM

I have updated this blog with the contents of the readme file, so you don’t have to extract the zip file each time you need to see how it should be installed (probably bad names/configuration sense I never remember it myself).

error Please login to comment.
Latest blogs
Composition Over Inheritance: Why Your Content Contract Is Not a Base Class

Inside the structural conformance pattern in SaaS CMS — from server-side inheritance to pipeline governance. A contract in Optimizely SaaS CMS is...

Vipin Banka | Sep 19, 2026

Optimizely Opti ID Integration: Why the API Key Was Missing from the DXP Management Portal

While working on an Optimizely CMS 12 Opti ID integration recently, we ran into an issue that initially appeared to be related to SSO authenticatio...

Madhu | Sep 18, 2026 |

Extending a Contract: What You Can Override

Contracts share fields across content types — but not every field setting can be overridden. Push the same contract onto several components, and CM...

Chirag Khanna | Sep 18, 2026 |

Building a Blazor Server UI Inside the Optimizely CMS 13 Admin Shell

What I learned shipping a Blazor Server UI inside Optimizely CMS 13 — Razor components in a NuGet package, the Blazor hub next to MapContent(),...

Stanisław Szołkowski | Sep 17, 2026 |