Missing Projects Refresh Risk Report

Categories:
Tags:
New to psLens? This page documents one specific report. To see how it runs in the product, what the output looks like, and how teams use it in practice, start with a live walkthrough.
Book a Demo Browse Reports
Tailored Operational Context
  • Target Database: —
  • Context Type: —
  • Alert Severity: —
  • Triggered Time: —
  • Firing Context: —

Missing Projects Refresh Risk Report

Report ID: projects-missing Category: Developer Tools

This page documents the report used to audit project risk in a target database before a database refresh.

Purpose

When refreshing a non-production PeopleSoft database (like TEST or DEV) with a copy of production (like PRD), code or metadata changes in TEST/DEV that have not yet been migrated to production are permanently deleted. This report identifies target database projects updated since a specific date that are missing or have older versions in the production database.

What It Detects

The report groups target projects into three risk categories based on their presence and versions in the source database:

High Risk: Missing in Source

Projects that exist in the target database but are completely missing in the source database. Overwriting the target database will delete these projects and their constituent objects.

Medium Risk: Newer in Target

Projects that exist in both databases, but the target database contains a newer version number or last updated timestamp. Overwriting the target database will revert these changes to the older version.

Low Risk: Identical or Older in Target

Projects that exist in both databases where the source database has an identical or newer version. These are safe to overwrite.

Tables Queried

PSPROJECTDEFN — Project Definitions

FieldDescription
PROJECTNAMEProject name (primary key)
PROJECTDESCRShort description
VERSIONVersion number
LASTUPDOPRIDLast updated by
LASTUPDDTTMLast updated timestamp

Parameters

ParameterRequiredDescription
source_dbYesThe name of the source/production database (e.g. PRD)
as_of_dateYesThe date to filter target projects (updated on or after this date)

The target database is selected from the primary database dropdown in the report runner.

Use Cases

  • Pre-refresh audit: Run this report before restoring a production database backup to a non-production database to identify developer work that needs to be backed up or migrated.
  • Unmigrated work tracking: Audit what projects have been created or modified in a test database but not yet migrated to production.