 |
 |
Archives of the TeradataForum
Message Posted: Fri, 10 Dec 2004 @ 20:42:52 GMT
Subj: | | Alert Policy and controlling access to dbcmngr.alertcontrol |
|
From: | | Anomy Anom |
<-- Anonymously Posted: Friday, December 10, 2004 14:37 -->
I've started the Teradata Manager windows service in order to collect some data, but I see that the user is logging on every minute and
according to access logging, it's selecting from and updating dbcmngr.alertcontrol. I haven't set up any alert policies and don't plan to use
them at this time. Is there any way to stop this overhead of checking & updating dbcmngr.alertcontrol, or else at least doing it less often? I'm
running Teradata Manager 6.0.0.6. Thank you.
| |