Octo for geodatabases and data quality
The Esri geodatabase is administered almost entirely through ArcPy: creating, upgrading, reconciling and posting versions, compressing, reindexing, validating topology and attribute rules. With read access to the database and the extracts, Octo can build the nightly routine with a report and alert, diagnose the health of an enterprise geodatabase and audit the quality of a cadastral database, all prepared for human review. System tables are not changed through SQL, and publishing to production, edit conflicts and topology exceptions stay with whoever administers the database.
Six possible deliverables, drawn from the survey. All of them start from reading the database or an extract; anything that changes data or schema runs only on the geodatabase administrator's order.
Can write the routine for reconcile, post, compress, index rebuilding and statistics updates, with a dry run first, guaranteed release of connections and a snapshot of states and delta tables before and after.
Deliverable: schedulable script + report and alertCan measure through read-only SQL the state tree, the versions holding back the compress, lineage depth, the A/D delta tables and the statistics, and add the Diagnose Version Tables log.
Deliverable: report with recommendations by severityCan validate topology and attribute rules on a copy of the database, add cadastral business rules in Python and assign outstanding items by department and owner, with the coordinates of each one.
Deliverable: list of outstanding items per teamCan prepare the creation of the enterprise geodatabase (Oracle, PostgreSQL, SQL Server) and the upgrade with a prerequisites check the day before, with the list of what changes and what needs a backup.
Deliverable: creation or upgrade runbookCan compare traditional and branch versioning for your workflows (direct connection, service, utility network, parcel fabric) and show what changes in the maintenance of each.
Deliverable: comparison for the administrator's decisionCan document the geodatabase version, registered datasets, attribute rules, topologies and the routine in force, and compare staging and production schemas with Esri's schema reports.
Deliverable: schema and routine recordThe same Octo cycle, applied to the geodatabase. Each arm has a narrow role; publishing, editing the official database and resolving conflicts belong to the administrator and the cadastral team.
Geodatabase type, DBMS and version, geodatabase version, traditional or branch versioning, registered datasets, topologies, attribute rules and what already runs at night.
System tables read-only, actual columns in the installed version, delta tables by registration_id, spatial types (ST_Geometry or PostGIS) and versioned views.
An administrator .sde file is a credential. Cadastral databases usually hold personal data (LGPD) and utility networks may be critical infrastructure: sending anything to an external service, including AI, is assessed with the client first.
Read-only SQL when measuring is enough; Esri tools when something must change; a copy or extract to validate; never write SQL against a geodatabase table.
Prepares routine, assessment and audit in ArcPy and SQL, with a dry run by default, guaranteed release of connections and the Esri page for each call noted in the file.
Before production, runs on a copy or in staging and checks by the numbers: states before and after, delta rows, number of outstanding items against a known sample.
Only with your OK, the routine goes into the scheduler of the environment the client approved. Running in production, reconcile, compress and version deletion stay with the geodatabase administrator.
Geodatabase version, routine in force, calibrated thresholds, accepted rules and exceptions. The next job starts from this record, and a script for one database is not assumed ready for another.
Octo does not edit the official database, publish to production or decide edit conflicts or topology exceptions. That belongs to the geodatabase administrator and the cadastral team.
The criteria Octo uses to choose. Esri tools remain the only way to change the geodatabase; SQL is for reading.
| Task | Path | Note |
|---|---|---|
| Creating an enterprise geodatabase | Create Enterprise Geodatabase (Oracle, PostgreSQL, SQL Server) | ArcGIS Server keycodes; PostGIS requires a database created by hand |
| Upgrading the geodatabase version | Upgrade Geodatabase, with the prerequisites check first | Backup; treat as irreversible |
| Nightly maintenance (traditional) | AcceptConnections, DisconnectUser, Reconcile Versions, Compress, Rebuild Indexes, Analyze Datasets | With a dry run and a before-and-after report |
| Maintenance with branch versioning | Reconcile Versions via the service URL; Prune Branch History | Compress does not apply |
| Geodatabase health | Read-only SQL + Diagnose Version Tables | Read-only |
| Cadastral quality | Validate Topology, Export Topology Errors, Evaluate Rules + rules in Python | On a copy of the database |
| Reading versioned data through SQL | Versioned view | The base table alone does not show the edits |
| Writing through SQL | Not recommended | Esri warns it can corrupt the geodatabase; the administrator's decision |
| Comparing schemas | Generate Schema Report and Compare Schema | HTML report since ArcGIS Pro 3.6 |
Three steps. Each one only makes sense after the previous one has shown results in your database.
A proposal, not a promise
With read access, you ask in administrator terms and Octo measures and explains.
Nightly maintenance now runs with a dry run, report and alert, and the quality audit with each extract.
The report history shows the database trend and prepares upgrades and schema changes.
Each point below has a source published by the vendor, the project or the responsible agency. The sources are in the next section.
4
points with a published source, each with its reference alongside.
Octo prepares everything, but does not sign. The document of record stays with whoever is accountable for it.
Gathers, calculates, organizes and produces the documents: spreadsheets, reports, maps and drafts.
Deliverable: material ready for reviewThe licensed professional reviews what Octo delivered before signing. If something doesn't add up, it goes back to Octo with the correction.
Step: review by whoever signsOcto does not sign. Designs, technical reports, ART/RRT, accountability reports and any official document are still signed by the licensed professional at the company or agency: here, the professional of record for the map or survey.
Signature: professional of record for the map or surveyEsri documentation used in the research, accessed October 29, 2026.
The assessment starts with read access to the database or an extract, without touching the official database. You get the numbers and a proposal for what can be automated in maintenance and quality, and decide with it in hand.
