Reporting overview
Reports summarize database activity over a period you choose. They answer questions the Console Portal's live views cannot: what happened last month, across every database, in a form you can file or hand to an auditor.
FPT Database Engine currently provides one report category: backup activity. It covers backup job runs across the databases in your scope for the period you select.
Two ways to get a report
| View reports | Configure report schedule | |
|---|---|---|
| Triggered by | You, when you need it | A recurring schedule |
| Period | Whatever you filter to | The cadence you set: daily, weekly, or monthly |
| Delivered as | A CSV file you download, after previewing on screen | A CSV file emailed to the recipients you name |
| Suits | Investigating a specific window, or a one-off request | Routine compliance, and record-keeping nobody has to remember to do |
The two are independent. Having a schedule does not stop you exporting on demand, and a manual export does not disturb the schedule.
What reporting does not do
Reporting is a record of what happened, not a monitor. It does not alert, and it does not show current state.
- For live metrics and dashboards, use Monitor database with FMON.
- To be told when something crosses a threshold, use Manage alert rules.
- For the audit trail of who changed what, use View Action Logs.
Next steps
- View reports to export backup activity for a period
- Configure report schedule to have it arrive by email
- Backup & Restore overview for what the report is reporting on