Appendices
This reference helps designers, operators, data administrators, and support staff identify database/driver requirements, exchange formats, files, terminology, and support procedures. Complete initial configuration through Chapters 4-5. For incidents, locate the failing stage in Chapter 7 before using these tables.
"Supported" means an implemented entry or handling path, not certification of every database version, driver, structure, or equipment combination. Actual capability depends on delivered components, architecture, license, role, and source limitations. File selection, connection, preview, and saved results are separate milestones.
All paths, identifiers, hosts, and incidents here are fictitious. Obtain approval and use test copies before writes, recovery, or output.
| Reference | Section | Use |
|---|---|---|
| Databases, drivers, architecture | 8.1 | Separate file/server/ODBC, then verify each workstation. |
| Import and export formats | 8.2 | Check the actual entry; capabilities are not symmetrical. |
| Extensions and backup inventory | 8.3 | Identify purpose/boundary, then inventory through Chapter 6. |
| Layouts, keys, synchronization, licensing | 8.4 | Use the distinctions, not assumptions from names. |
| Incident submission and redaction | 8.5 | Control impact, record facts, and submit officially. |