Logging Application Block - Databases Trace Listener???

[amitos]

Hi!

I consider using the Logging Application Block, Enterprise Library, Jan
2006 in a major project. To date, I've found that some of its features
are not very well documented.

One important thing is logging to a database. I tried configuring a
database trace listener in the "Enterprise Library Configuration".
There I'm stuck. Stored procedures? Which ones exactly? What parameters
do they take? I'm pretty confused. It also seems it implies the use of
the database application block, which I don't want to use. Another
option may be writing my own provider, but that starts making this
library less of an abstraction.

Have anyone experimented with database logging in this context? Any
help is welcome. Thanks!

Amit

 

[Shaun McDonnell]

I have used to the Logging Application Block and it does require use of the
DAAB. However, this is good architecture because it is based on reusability.
The Enterprise Library comes with all of the scripts you need to install
the database as well as the stored procedures to log to the database. The
EHAB also makes use of these features for logging exceptions. Let me know
if you have anymore questions. Good luck.

Shaun C McDonnell
Solutions Architect

 

[amitos]

Thanks Shaun!

I were looking for the scripts but am unable to find them. In what
directory do they reside?

Amit

 

[ProblemQueen]

the directory is xxx/Microsoft Enterprise Library January 2006
\src\Logging\TraceListeners\Database\Scripts

 

[ProblemQueen]

the directory is xxx/Microsoft Enterprise Library January
2006\src\Logging\TraceListeners\Database\Scripts

 

[ProblemQueen]

the directory is xxx/Microsoft Enterprise Library January
2006\src\Logging\TraceListeners\Database\Scripts

 

[amitos]

Got it. Thanks!

Amit