Octo for spatial databases in ArcGIS Enterprise
In ArcGIS Enterprise, the spatial database (PostgreSQL with PostGIS, SQL Server, Oracle, SAP HANA or Db2, on your server or in the cloud) is where parcels, networks and ERP tables meet. With read access, Octo can join the IPTU (property tax) registry to the parcels through a view, audit spatial types, SRIDs, indexes and privileges and prepare the migration from ST_Geometry to PostGIS with numerical verification. Esri prohibits writing to versioned data through SQL; creating roles, granting privileges and publishing services stay with the DBA and the portal administrator.
Six possible deliverables, drawn from the survey. All of them start from reading the catalogs and tables; anything that creates objects, grants privileges or publishes runs only on the order of the DBA and the portal administrator.
Can join the IPTU registry, CRM or customer registry to the features through a spatial view, without copying geometry, and point out parcels without a registry entry, registry entries without a parcel and mismatched areas.
Deliverable: view, query layer and service draftCan list each spatial column with its type (ST_Geometry, PostGIS geometry or geography), SRID and shape, what is registered with the geodatabase and what is a standalone table from another system.
Deliverable: inventory comparable month to monthCan find roles with SUPERUSER, CREATEROLE or BYPASSRLS, write access open to PUBLIC, write access on system tables and RLS enabled without a policy, and write the commented correction SQL.
Deliverable: report by severity + SQL for the DBACan read the EXPLAIN of a query layer's SELECT, find spatial tables without a GiST index, stale statistics and joins without indexes, and propose the fix outside peak hours.
Deliverable: assessment with the execution planCan compare your database with the requirements of RDS, Aurora, Azure Database for PostgreSQL and Cloud SQL (PostGIS only) and prepare the copy of each ST_Geometry class with numerical verification.
Deliverable: class-by-class migration planCan record which database and version support each service, what is referenced and what was copied, what lives in ArcGIS Data Store and who has which privilege.
Deliverable: eGIS architecture mapThe same Octo cycle, applied to an eGIS database. Each arm has a narrow role; creating roles, granting privileges, registering data stores and publishing belong to the DBA and the portal administrator.
DBMS and version, where it runs (own server or cloud service), whether it has a geodatabase, which services point to it, what lives in ArcGIS Data Store and which in-house systems write to the tables.
Spatial types per column, SRIDs, what is registered with the geodatabase, join keys with the ERP (registration number, customer code) and duplicates before any view.
Read-only role for query services, no SUPERUSER or BYPASSRLS on application connections, RLS where the ERP requires filtering, personal data kept out of the view (LGPD) and sending to external services assessed first.
Views and query layers to read another system; registration with the geodatabase when editing in Pro is needed; referenced data instead of copied; Esri tools, never write SQL, on versioned data.
Prepares views, audit scripts, query layer and migration scripts, with a dry run by default and the Esri, PostgreSQL or PostGIS page noted in each file.
In staging: view count against the source tables, EXPLAIN of the layer's SELECT, count, area and SRID before and after a migration.
Only with your OK: the DBA runs the approved SQL; the administrator registers the data store and brings up the service from the prepared .sd.
Which database supports each service, what is referenced and what is a copy, roles and privileges in force, the official SRID and the certificate for each migration.
Octo does not create roles, grant privileges, write to geodatabase tables or publish services. That belongs to the DBA and the ArcGIS Enterprise administrator.
The criteria Octo uses to choose. SQL is for reading and for objects outside the geodatabase; what is registered and versioned changes only through Esri tools.
| Task | Path | Note |
|---|---|---|
| Geodatabase on a managed database | Enable Enterprise Geodatabase | PostgreSQL in the cloud: PostGIS only |
| Reading another system's table on the map | Make Query Layer | Read-only on the map; unique identifier with no nulls |
| Joining ERP and parcels | Spatial view + query layer | Read-only layer in Portal |
| Table created through SQL with geodatabase functions | Register With Geodatabase, as the owner | A registered view cannot go into a feature service |
| Publishing without copying | Register the database (AddDataStoreItem) and copyDataToServer = False | Without registration, the server copies |
| Giving a user access | Change Privileges | Branch versioning: access through sharing in the portal |
| Auditing the database | Catalog SQL + audit script | Read-only |
| Moving ST_Geometry to the cloud | Copy with PG_GEOMETRY + verification | Migrate Storage only on Oracle and SQL Server |
| Analyzing in Snowflake, BigQuery or Redshift | Warehouse connection + query layer | No geodatabase and no editing |
| Writing to versioned data through SQL | Prohibited (branch) or only through the versioned view (traditional) | Esri warns; the administrator's decision |
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 as a DBA would and Octo measures and explains.
Each integration with an ERP, registry or CRM starts as a view, query layer and service draft, with the discrepancy check.
The audit history shows the database trend and prepares migrations and upgrades.
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, PostgreSQL and PostGIS documentation used in the survey, accessed October 29, 2026.
The assessment starts with a read-only user on the catalogs, without touching any table. You get the inventory, the discrepancies and a proposal for what can be integrated and fixed, and decide with it in hand.
