In my opinion, the ability to propogate schema changes from a parent gdb to a child gdb is very limited at this point in time. In looking at Working With Schema Changes in the Esri help docs the tables says you can add featureclasses/tables but if you read just below the table it says "Adding a feature class or table to a replica cannot be accomplished with the tools discussed above. Instead, you need to run ArcObjects code. View a sample of this code". So while it is true, the method to do this takes a considerable amount of effort, especially for those who are not familar with ArcObject.
In addition, attachments are becoming more popular especially with ArcGIS Online, and the ability to add photos to features while in the field is an excellent enhancement to ArcGIS. On the other hand, since attachments use a relationship class we are not able use any Esri tools to add relationship classes to a replica so now it becomes more cumbersome to add attachments at the Parent gdb level and propogate those changes to the child.
What I would like to see is replication suppport most if not all levels of changes to the geodatabase. For example, if I add a featureclass or table to the parent, I should be able to run a tool that would add those changes to the existing replica in the child gdb. Additionally since attachments are now what I would consider to be a integral part of the geodatabase, then relationship classes should also be support as schema changes to a replica.
I understand the more complex objects like geometric networks and topologies being an issue but objects like featureclass, tables, and relationship classes should be supported. Additionally, not having to use ArcObjects to add featureclasses and tables to the replica would also be an excellent enhancement.
As data continues to grow and become more complex, we need a simplified method of dealing with changes at the parent gdb and propogating those changes to the child gdb's without having to take down our systems for maintenance. We live in a world which expects 24/7 access, "thanks a lot Google", lol. So we need tools and methods for making these changes which do not require us to take the system down for extended periods of time but merely refresh or restart services. Registering replicas and copying data can take a considerable amount of time depending on the data.
Just wondering if someone has tried using this sample GP tool. It states that it makes it possible to add a feature class to a replica and then sync the changes. The tool was written for 10.0, but may work fine in 10.1 too.
Geodatabases change. We constantly add new layers of information as we continue to grow our GIS program. Esri please update replication to allow for addition or name changes of feature classes and tables.
