Hi Rod,

according to IB LogManager 2.0 I can say, that none of my customers
has mentioned any significant performance decrease so far.

I did some testing during the development of IB LogManager by
pumping >100.000 records from different application instances into
the database (a full logging defined on tables and *all* their
columns). Yes it slows some things down, but logging so many
changes is really the worst case, which you probably will not
find in a real production system ...

Haven't heard any negatives using many triggers for that so far.

Regards,
Thomas Steinmaurer
IB LogManager 2.0 - The Logging/Auditing Tool for InterBase and Firebird
http://www.iblogmanager.com

> -----Original Message-----
> From: rodbracher [mailto:rod@...]
> Sent: Monday, June 24, 2002 2:39 PM
> To: ib-support@yahoogroups.com
> Subject: [ib-support] Measuring Trigger Overheads
>
>
> Hi
>
> Is there a tool that can be used to measure overhead of introducing
> triggers to the db. This would be relavent if I put an
> update/insert/delete trigger on say 100 relations - each writing to
> a "log" relation - obviously this will create a lot of triggering if
> there were 20 clients working at the same time.
> Of course this would all be server side processing but would have to
> see if this would effect the speed clients could access info ( At a
> human-noticeable ).
>
> Thanks
>
> Rod
>
>
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>
>