Starting in version 6.0, database auditing was added to the P6 database. Auditing is a method to log the edits, additions and deletions made by users of the Primavera application. Every change made by a user results in Data Manipulation Language or DML (INSERT, UPDATE or DELETE statements) execution against tables in the database. Every application table in the schema has its own auditing trigger that can log the changes to the table whenever and by whomever makes the change. Because the trigger is owned by the database schema owner there is no way to bypass its execution.
In General, auditing does not take affect until the user creates a new session after auditing is enabled. Additionally, auditing does not stop auditing active sessions (sessions established prior to disabling) until the session is terminated. For example, a user is logged in to application and auditing is enabled. The user will not be audited until the customer closes out of the application and logs in again.
The commands depends on what version p6 and and if you are using SQl or orcale as you datas base.
Version 15.2, database auditing can be configured from within P6 (web) without the need to run any stored procedures against the database directly.
To access the database auditing application settings:
Member for
16 years 3 monthsStarting in version 6.0,
Starting in version 6.0, database auditing was added to the P6 database. Auditing is a method to log the edits, additions and deletions made by users of the Primavera application. Every change made by a user results in Data Manipulation Language or DML (INSERT, UPDATE or DELETE statements) execution against tables in the database. Every application table in the schema has its own auditing trigger that can log the changes to the table whenever and by whomever makes the change. Because the trigger is owned by the database schema owner there is no way to bypass its execution.
In General, auditing does not take affect until the user creates a new session after auditing is enabled. Additionally, auditing does not stop auditing active sessions (sessions established prior to disabling) until the session is terminated. For example, a user is logged in to application and auditing is enabled. The user will not be audited until the customer closes out of the application and logs in again.
The commands depends on what version p6 and and if you are using SQl or orcale as you datas base.
Version 15.2, database auditing can be configured from within P6 (web) without the need to run any stored procedures against the database directly.
To access the database auditing application settings: