EGMP common mistakes
EGMP · Understand the traps and how to avoid them.
Assuming a spatial type or historical DBMS list applies to every current platform.
A familiar label or isolated operation does not establish the actual supported model, authority, dependency or verified outcome.
What to do instead
Check the supported release, database, clients and data-type prerequisites.
Copying one feature class and assuming all dependent relationships were preserved.
A familiar label or isolated operation does not establish the actual supported model, authority, dependency or verified outcome.
What to do instead
Verify relevant origin/destination data, relationship classes and dataset behavior.
Deleting repository rows to bypass a named-version edit lock.
A familiar label or isolated operation does not establish the actual supported model, authority, dependency or verified outcome.
What to do instead
Confirm active ownership and use supported authorized session/version administration.
Treating offline feature-service sync as identical to classic geodatabase replication.
A familiar label or isolated operation does not establish the actual supported model, authority, dependency or verified outcome.
What to do instead
Select the actual supported mechanism and its dataset/versioning prerequisites.
Applying traditional Compress expectations to branch temporal history.
A familiar label or isolated operation does not establish the actual supported model, authority, dependency or verified outcome.
What to do instead
Use maintenance appropriate to the actual model and retained-history requirements.
Disabling required validation merely to make a bulk load faster.
A familiar label or isolated operation does not establish the actual supported model, authority, dependency or verified outcome.
What to do instead
Preserve a supported accountable validation and recovery path and verify actual data outcomes.
Calling an old four-product diagram a timeless complete current checklist.
A familiar label or isolated operation does not establish the actual supported model, authority, dependency or verified outcome.
What to do instead
Verify actual release/platform storage, proxy, instance and role requirements.
Equating a managed hosting store with every registered enterprise database.
A familiar label or isolated operation does not establish the actual supported model, authority, dependency or verified outcome.
What to do instead
Trace where the relevant data actually lives and who manages it.
Adding installed cores and ignoring the one-server-failed condition.
A familiar label or isolated operation does not establish the actual supported model, authority, dependency or verified outcome.
What to do instead
Calculate surviving usable resources under the actual required failure model.
Treating high availability as protection against every deletion or corruption.
A familiar label or isolated operation does not establish the actual supported model, authority, dependency or verified outcome.
What to do instead
Use independently recoverable backups and a tested recovery plan within its actual scope.
Rebuilding a portal before examining an isolated registered-source error.
A familiar label or isolated operation does not establish the actual supported model, authority, dependency or verified outcome.
What to do instead
Trace the actual service/data path, credentials and logs with safe supported checks.
Assuming an unsupported rolling upgrade preserves all services.
A familiar label or isolated operation does not establish the actual supported model, authority, dependency or verified outcome.
What to do instead
Follow the actual release/platform compatibility and downtime requirements.