Project Checker

Use the Project Checker to assess the health of the data that constitutes projects. The project checker searches for data that violates unique key constraints, foreign key constraints, and P6 Professional business rules. Violations of business rules, foreign keys and unique key constraints in a database are not necessarily a problem, but can be an indication that a database contains orphaned data that could be cleaned up.

If P6 Professional is using Oracle, Microsoft SQL, or using Cloud Connect, only users with Admin Superuser or Project Superuser rights can access the Project Checker. Users with Project Superuser rights can only run the Project Checker against the projects for which they are a Project Superuser.

If P6 Professional is using SQLite, any user can access the Project Checker.

Business rule checks

Business rules in P6 Professional determine how data is structured and works together to create useful projects. For example, it is P6 Professional business rules that ensure that a baseline can only be associated with one project at a time, and that if an activity has resources assigned one of them must be assigned as the primary resource.

Foreign key checks

Foreign keys link data together. For example, foreign keys determine which activities belong to which projects, the roles assigned to each resource working on an activity, and how activity code values are associated with activity codes.

Unique key checks

Unique key constraints ensure that data items do not conflict with each other. For example unique keys prevent there being two activities with the same ID in the same project, or two projects with the same ID.

Tips:


Last Published Tuesday, March 4, 2025