Define when to flush log entries to database in Enterprise Library 4.1

132 Views Asked by At

I'm trying to create a custom database trace listener based on the FormattedDatabaseTraceListenerData and I'm having some doubts regarding its performance. What's the best way to cache in-memory logging entries so less transactions/connections to write logging data are made?

I'm using Enterprise Library 4.1. I think I have seen this type of caching options somewhere but I lost track of it.

Trace Listener MSDN

0

There are 0 best solutions below