Hi Calvin,

Yes, it doesn't surprise me that activity log rows numbering in the
millions will take several minutes to process (though 20 minutes does seem
like a long time, but that can also depend on other server activity).
Without knowing more about your intentions and time constraints, I'm not
convinced that you necessarily need to scrap the idea; though I agree that
for real-time alerts this may not be feasible.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 07/12/2004
09:28:51:

> Hi Andrew,
>
> Thank you so much for resolving my questions. Really appreciate the in
depth
> answer you have provided me.
>
> I decided to query the TSM server to see how many rows I have stored in
my
> actlog. Below is the output.
>
> tsm: TSM_SERVER_01>select count(*) from actlog
> ANR2963W This SQL query may produce a very large result table, or may
require
> a significant amount of time to compute.
>
> Do you wish to proceed? (Yes (Y)/No (N)) y
>
>  Unnamed[1]
> -----------
>     6,212,914
>
> Guess I can scratch out the idea on using the TSM Reporting tools for
sending alerts.
> =(
>
> Thanks again!