Writing an audit trigger for the operations you'd like to monitor
(then assign it to all your application's tables) to perform the
auditing may be one easy way of doing so, this trigger would log the
operations to some other table.
Allan.
On Thu, Feb 25, 2010 at 7:36 PM, Andy Yoder <ayoder@airfacts.com> wrote:
> Does anyone know of a tool (or a way to use the database catalogs) that can
> analyze function code/queries accessing the database to pull out a list of
> the fields used in a set of tables. Basically we are importing a lot of
> data from another source, and we are trying to determine what percentage of
> the data we are actually using at this point . We have hundreds of stored
> procedures, and combing through the code would not be practical.
>
>
>
> Thanks.
>
>
>
> --Andy
>
>
>
>
>
>