Sibghat,
You can always try to export your child version feature class to a file geodatabase; this will ensure you have a copy of your 20,000 edits. Name the export something obvious (Dataset_xxx_child_edits).
Is this the only feature class you have edits in? If there are additional feature classes, then you might want to back them up as well.
Now, if there are hundreds or more feature classes with edits in them, please let me know before continuing with this suggestion:
I would recommend trying:
After you have backed up all your edits, delete your child version. Compress your database to ensure it returns state “0”.
- Make a copy of your original parent version feature class (with the data that was not updated) in the same database, call it "_backup" at the end of the name.
- Use arcpy.TruncateTable_management() to truncate your original feature class. This will delete all your data in the feature class (why step one is essential in backing up your original Parent version content).
- Utilize arcpy.Append_management() to load the data from your child version (Dataset_xxx_child_edits) backup to the parent feature class.
- Append will indicate if you have a schema issue, you will not be able to append the new data if there was a schema change.
- If this runs successfully, you have applied your new edited data changes to the original parent. Check this manually (geometries, attributes).
- If this tool runs unsuccessfully without a schema issue, please post.
- After verification that new data is in original parent feature class
- Delete your child backup (Dataset_xxx_child_edits).
- Delete your copied original parent dataset "_backup"
- Create a new child version of your geodatabase.
Please post any follow up information or questions.
Regards,
Alex
