By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
449,221 Members | 1,604 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 449,221 IT Pros & Developers. It's quick & easy.

Logging Application Block - Databases Trace Listener???

P: n/a
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

Apr 30 '06 #1
Share this Question
Share on Google+
7 Replies


P: n/a
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
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

Apr 30 '06 #2

P: n/a
Thanks Shaun!

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

Amit

Shaun McDonnell wrote:
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
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


May 1 '06 #3

P: n/a
the directory is xxx/Microsoft Enterprise Library January 2006
\src\Logging\TraceListeners\Database\Scripts
amitos wrote:
Thanks Shaun!

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

Amit

Shaun McDonnell wrote:
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
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


May 10 '06 #4

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

May 10 '06 #5

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

May 10 '06 #6

P: n/a
Got it. Thanks!

Amit

May 10 '06 #7

P: 1
hi all,
i used the LAB to log on a database, it works well with the Logging Database that comes with it, but is it possible to make my own database?, if possible,how the LAB will deal with my Database??
May 17 '06 #8

This discussion thread is closed

Replies have been disabled for this discussion.