Archives of the TeradataForum
Message Posted: Thu, 21 Mar 2002 @ 12:52:54 GMT
Nice to hear from you again Dave. I agree with your comments and would like to elaborate a little further...
Yes, the PI of the acclogtbl does cause lumpy distribution-but this is an issue for any application if it uses generic sessioning, and for Queryman if you logon once in the morning and keep the session open-a lot of people do this-and I'm one of them!.
If access logging is carefully defined and not a simple every instance of every statement, ie columns,tables etc then this reduces the volume therefore the 'lumpiness'. It is not necessary to log all statements issued agains the CRM system tables (these are the high volumes talked about) as these are in the main PI single row retrievals,updates,deletes.
It is advisable that the data for generic sessions in particular, is extracted from dbc.acclogtbl each evening/half day/hour depending on the user volumes and placed in a very similar table that has a PI on logdate,logtime (Ithink these are the only two columns). This will then reduce the 'lumpiness' and poor performance from acclogtbl and still enable historical analysis of these generic sessions.
I am fairly sure that the removal of the generic logon is on the feature request list, but it will do no harm if you request this via your account manager/project manager.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|