Sample deliverable · Data & Databases
Sample assessment report: database upgrade readiness
The structure and depth of the written plan you receive at the end of a paid assessment, shown with fictional systems.
Sample / template. Fictional systems and figures that show the format and depth of what you receive. Not a client deliverable.
Prepared for: Example Co. (fictional) · Scope: 6 PostgreSQL and 2 MongoDB databases on AWS · Length of a real report: typically 15–30 pages
1. Executive summary
Four of six PostgreSQL instances run version 13 or 14 and will move to paid Extended Support when standard support ends. Two MongoDB replica sets run 6.0, which is past end of life. We recommend upgrading in three waves over six weeks, starting with the lowest-risk reporting databases. The fixed fee for delivery is in section 6.
2. Inventory
| Database (fictional) | Engine / version | Size | Support status | Risk |
|---|---|---|---|---|
| orders-db | PostgreSQL 13 | 1.2 TB | Extended Support | High |
| billing-db | PostgreSQL 14 | 400 GB | Standard until Feb 28, 2027 | Medium |
| reporting-db | PostgreSQL 14 | 2.1 TB | Standard until Feb 28, 2027 | Low |
| events-rs | MongoDB 6.0 | 800 GB | End of life | High |
3. Findings and risk register
| # | Finding | Impact | Recommendation |
|---|---|---|---|
| R1 | Extension pg_example pinned to an old release | Blocks upgrade | Upgrade extension in a prior change |
| R2 | No restore tested in the last 12 months | Unknown recovery time | Restore test before wave 1 |
| R3 | MongoDB drivers on two services too old for 8.0 | Application errors | Driver upgrade in application sprint |
4. Upgrade approach
- PostgreSQL: RDS blue/green deployments, rehearsed per wave, with measured switchover
- MongoDB: rolling upgrade 6.0 to 7.0 to 8.0, one member at a time
- Rollback: switch back to blue environment or restore from snapshot, both rehearsed
5. Plan and timeline
| Wave | Databases | Window | Duration |
|---|---|---|---|
| 1 | reporting-db | Weekday evening | Week 2 |
| 2 | billing-db, events-rs | Weekend | Week 4 |
| 3 | orders-db | Weekend | Week 6 |
6. Fixed quote
A single fixed fee for all three waves, including rehearsals, runbooks and hand-over, with the assessment fee credited. Changes to scope are agreed in writing before they are made.
7. Assumptions and out of scope
- Application testing is performed by your team within each window
- Out of scope: schema redesign, new features and engines not listed above
Appendices
Full inventory export, query baselines, parameter differences, and the draft runbook for wave 1.
Want this for your systems?
Every paid assessment ends in a document like this, with your real systems, risks and a fixed quote. The fee is credited to the project.