← ClaudeAtlas

enterprise-geodatabaseslisted

Reading and safely working with Esri enterprise geodatabases (SDE) on Oracle, SQL Server and PostgreSQL, covering versions, reconcile and post, branch vs traditional versioning, a protected DEFAULT, domains and subtypes, relationship classes, attribute rules, archiving, ST_Geometry vs SDO_GEOMETRY vs SQL Server geometry, and versioned views vs base tables. Use it when asked to "query the SDE", "edit the enterprise geodatabase", "reconcile and post", "what do these codes mean", "why does SQL show different rows than ArcGIS Pro", or before touching any versioned or registered table.
wiatrek-kevin-s/columbus · ★ 2 · API & Backend · score 68
Install: claude install-skill wiatrek-kevin-s/columbus
# Enterprise geodatabases An enterprise geodatabase (EGDB, "SDE") is an ordinary Oracle, SQL Server or PostgreSQL database with Esri's system tables and rules on top. The rules (versions, domains, relationship classes, attribute rules, editor tracking) live in the geodatabase, not in the database, so **SQL sees the tables but not the rules**. Most mistakes come from forgetting that. ## General practice (with or without Columbus) ### 1. The one rule: never edit DEFAULT directly DEFAULT is the published, trusted state of the data. Edit in a **named child version**, check it, then reconcile and post. Even if you have the rights to edit DEFAULT, do not: there is no review step, no undo for other users, and a bad edit is live at once. - DEFAULT's access is usually **protected**: everyone can read it, only its owner (often `SDE` or the data owner) can edit it or post to it. A "protected" error when posting means you need the owner or a QA role to post. That is the design working, not a bug. - Do not edit registered tables with SQL (`INSERT`, `UPDATE`, `DELETE`) or with tools that bypass the geodatabase. SQL skips domains, subtypes, attribute rules, relationship class behaviour (composite deletes, messaging), editor tracking and GlobalID generation, and on versioned data it can write rows that ArcGIS never shows. - If someone asks for a bulk fix, propose it as a reviewed edit in a named version. ### 2. Traditional vs branch versioning | | Traditional | Branch | | --