In a perfect world, an entire SDE could be backed up to a GDB. With one click, one tool. All versions, all archiving.
In reality, it seems we need to create a replica for every version. And replicas are not "smart", you have to destroy one and re-create it if you add a field or change schema. It would be great if we could edit replications or ideally they could automatically stay up-to-date with the schema (option of choosing favoring parent or child)
But also, it appears replication does not back up Archive tables. Is that right?
It would be great to let replication copy Archiving tables; at least optionally.
I hope there will be focus on SDE (vs AI or 3D) over the next year. A lot of good backend features like Web Hooks have been created. Good stuff. Continue on this path and pick up some longstanding (years/decades) Ideas on here, like better QA interface for Versions, replication, etc.
