QAD Progress OpenEdge Database Maintenance Checklist
This checklist lists the routine DBA tasks for on-prem QAD Enterprise Edition and Standard Edition databases on Progress OpenEdge 10.2B to 12.x, with the Progress utility for each. It is grouped by frequency, plus pre-upgrade and disaster recovery tasks.
0 of 28 items complete
7 critical items still open - these are the highest-risk gaps.
1. Daily
2. Weekly
3. Monthly or quarterly
4. Before a QAD patch or upgrade
5. Disaster recovery
Critical items protect recoverability: a verified backup, working after-imaging, a tested restore and control of BI growth.
Want a health check on your QAD database?
Send us your .lg excerpt, .pf file and dbanalys output and we will flag the risks we see.
Optional. The tool and every export work without this. No spam.
How to use it
Use the daily and weekly groups as a run book and the monthly group as a maintenance window plan. Script the checks you can (probkup, prorest -vp, dbanalys, log scans) and keep their output, because trends tell you more than any single run. Tick items in the tool and export to PDF as evidence for auditors or IT management. QAD installs typically have several databases (qaddb, admin and help databases, sometimes custom ones), so repeat the list per database.
The utilities behind each item
probkup online backs up a running database; prorest -vp and -vf verify a backup without restoring it. rfutil manages after-imaging: aimage begin enables it, the AI archiver copies full extents, and roll forward applies them to a restored backup. proutil runs analysis (dbanalys, tabanalys, idxanalys), index work (idxbuild offline, idxcompact online), truncate bi and holder. prostrct add and statistics manage extents and show area use. promon shows activity, locks, buffers and transactions. Check the exact qualifiers in the OpenEdge Database Management guide for your release.
- Backup: probkup, prorest.
- Recovery: rfutil.
- Analysis and repair: proutil.
- Structure: prostrct; monitoring: promon.
Worked example: BI file growth
A user runs a large report with a transaction open overnight, and the BI file grows by several GB. promon shows the oldest active transaction and the user behind it. The fix is to end that session and correct the program, not to truncate the BI while the database runs: truncate bi needs the database offline. Daily checks of the log and BI size catch this before the disk fills.
Version differences and gotchas
OpenEdge 12 removed the classic AppServer and WebSpeed brokers in favour of PASOE, so asbman and wtbman checks apply to 11.x and earlier. After-imaging must be planned around offline utilities; some operations require AI to be disabled and a new backup taken afterwards. idxbuild needs the database offline and enough temp disk. A backup that has never been restored is not a backup: test restores at least quarterly.
Frequently Asked Questions
How do I back up a QAD Progress database while users are working?
Use probkup online with the database name and target file, for example probkup online qaddb /backup/qaddb.bak. It takes a consistent backup while users stay connected. Combine it with after-imaging so you can roll forward from the backup to the point of failure, and verify each backup with prorest -vp.
What is after-imaging in OpenEdge and why does QAD need it?
After-imaging writes every committed change to AI extents. With a backup plus archived AI files you can restore and roll forward to just before a failure, instead of losing everything since the last backup. Enable it with rfutil aimage begin after a backup, and use the AI archiver so full extents are copied away automatically.
When should I rebuild indexes on a QAD database?
When idxanalys shows low utilization or after large purges and archives. idxcompact runs online and is the first step for fragmented indexes. A full proutil idxbuild needs downtime and temp space, so schedule it in a maintenance window. Always back up first and record timings so the next window is planned accurately.
Can I truncate the BI file while QAD is running?
No. proutil -C truncate bi requires the database to be shut down. If the BI file is growing, find the cause first: usually a long-running transaction visible in promon. After a planned shutdown you can truncate it and review the BI cluster size and transaction handling in the programs involved.
If you want your team to ask QAD questions in plain English on your own servers, we can build that on top of a database you already maintain this way.
Related Tools
QAD Progress OpenEdge Storage Area Sizing Calculator (Records per Block)
Work out records per block, block count and storage area size today and after growth for a large QAD table such as tr_hist or ld_det.
Developer ToolsQAD Progress Connection Parameter File Generator
Generate .pf parameter files for connecting a Progress client to a remote QAD database over TCP.
Other ERPsQAD EE Key Fields Reference (pt_mstr, so_mstr, sod_det, wo_mstr, po_mstr)
Searchable list of the QAD Enterprise Edition fields report writers use most, by table, with type, meaning and the menu program that maintains them.
ERP Migration & SelectionQAD EE to Adaptive ERP Migration Checklist
A grouped checklist for planning and executing a move from QAD Enterprise Edition to Adaptive ERP, from inventory to hypercare.
More Other ERPs tools
See all- QAD Menu Program Reference Worksheet
- QAD Core Tables Reference
- Infor VISUAL Work Order Status and Structure Reference
- Infor VISUAL Manufacturing Scheduling Checklist
- Infor XA (MAPICS) Period End Close Checklist
- Infor VISUAL Database Table Reference
- Infor XA (MAPICS) Application Module Reference
- IBM i Commands for Infor XA Administrators Reference
- Acumatica Generic Inquiry Design Template
Keep exploring
Free tools
- QAD Progress OpenEdge Storage Area Sizing Calculator (Records per Block)Work out records per block, block count and storage area size today and after growth for a large QAD table such as tr_hist or ld_det.
- QAD Progress Connection Parameter File GeneratorGenerate .pf parameter files for connecting a Progress client to a remote QAD database over TCP.
- QAD Progress 4GL Query GeneratorFill in domain, site and a part prefix to get ready-to-run, read-only Progress 4GL queries against common QAD EE tables.
ERP fixes and how-tos
- How to Back Up and Restore a QAD Progress Database with probkup and prorestStep by step guide to online backup of a QAD Progress database with probkup, incremental backups, verification, and restore with prorest, plus the traps to avoid.
- How to Add a Private AI Layer to QAD Enterprise Edition On-PremHow to add a private, on-prem AI assistant to QAD Enterprise Edition: OpenEdge SQL access, QXtend write-back, domain security, GPU sizing and rollout.
- AI for Epicor 9 and Vantage on Progress OpenEdge: A Private ArchitectureAdd a private AI assistant to Epicor 9 or Vantage on Progress OpenEdge: SQL-92 read path, replication, local LLM, permissions and honest limits.
Guides
- How to Set Up Database Backup Automation in SyteLineAutomate SyteLine database backups with SQL Server maintenance plans, transaction log management, and disaster recovery procedures for Infor CloudSuite Industrial.
- SyteLine Database Backup and Recovery StrategyPlan database backup and disaster recovery for Infor SyteLine SQL Server environments. Configure full, differential, and transaction log backup strategies.
- ERP Disaster Recovery Planning and Cloud Recovery Options for ManufacturersERP disaster recovery options for manufacturers: compare cloud and on-prem recovery, set RTO and RPO, sequence integrations, and test failover.
AI on your ERP
- AI for QAD in Automotive: Schedules, Traceability and IATF Evidence From Your Own OpenEdge DataPrivate AI on QAD Adaptive ERP for automotive suppliers: schedule releases, ASN, lot traceability and IATF 16949 evidence, read-only, on-prem or sovereign.
- AI for QAD Adaptive ERP in automotive and industrial manufacturingAdd AI to QAD Adaptive ERP or Enterprise Edition for automotive and industrial manufacturing, grounded on QXtend and QAD's API layer, on-prem or private cloud.
Integrations
- How to add AI agents to QAD Adaptive ERPBuild AI agents on QAD Adaptive ERP: a tool layer over QXtend and read-only OpenEdge access, MRP exception triage, PO expediting and human approval before writes.
- How to connect Power BI to QAD Adaptive ERPConnect Power BI to QAD through ODBC to an OpenEdge replica, QAD analytics exports or a warehouse. Gateway setup, key manufacturing dashboards and natural-language Q&A.