AlexArcPy/registrant

Create replica tab for enterprise geodatabases

tom-montgomery opened this issue · 9 comments

Managing replicas is not very easy with the ArcGIS GUI As you cannot copy the replica data list (which tables/feature classes are included in replica) easily to manage the replica data.
It is possible with SQL Server Management Studio, but it would be nice if it were included in the registrant HTML output.
Replica tab could include:
replica names
replica data
replica history

@tom-montgomery , excellent idea! Let me see if this information is exposed via arcpy. I'll get back to this issue this week.

Hey @tom-montgomery , arcpy does expose quite some information about the replicas, so I am adding the Replicas section to the report. However, to get the list of the datasets I'd need to export the geodatabase schema into an XML first and then parse it. I am working on this.

What do you think would make most sense - having the information about the datasets participating in the replica for each replica as a comma separated list (Datasets column)

fig1

or as a property for each individual table/fc (Replica column)

fig2

?

Awesome thanks for looking considering it.
I would prefer to have the replica datasets as an entire list like in your first screenshot. The main reason is if I need to add a feature class or table to an existing replica it requires re-creating the entire replica as you cannot simply add a single new data. So, yes the concise list would be best from the enterprise management perspective.
This may be out of scope of this project but really what would be ideal would be auto creation of an MXD of the existing replica datasets for easy re-creation.

@tom-montgomery , no worries! Thanks for the clarification, this makes perfect sense. I am able to parse the datasets within the replica in the database, I've decided to make a nice list of datasets instead of the comma separated text.

I've also decided to include both the dataset name and the target name. For example, when reading the datasets in the replica inside a file geodatabase that is a one-way replica (of an SDE geodatabase), then it would be "cities -> DbName.DBO.Cities". This is how it looks.

For SDE gdb:

fig1

For file gdb:

filegdb

As I am anyways have access to the XML of the replica, maybe there is something else you would like to be reported? I have added the Creation date as you can see. You can explore the information about replicas if you export the replicas into an schema XML file using the GP tool http://desktop.arcgis.com/en/arcmap/10.3/tools/data-management-toolbox/export-replica-schema.htm.

When this is set, I am ready to push so you could start using the latest version :)

@tom-montgomery , regarding your request

what would be ideal would be auto creation of an MXD of the existing replica datasets for easy re-creation.

I would really like focusing on reporting in this particular package, so this is not something I'd consider adding. However, by all means, please ask a question on https://gis.stackexchange.com/ and me or someone else would be able to help you writing a Python script that would re-create an .mxd file with the datasets listed in an existing replica, doesn't sound hard at all, can be written under 20-30 lines of Python.

Awesome! I look forward to the implementation, thanks.

Just published the v0.2, feel free to grab and install. Please let me know anything you think could make reporting replicas (or anything else in geodatabase) more useful to you!

@tom-montgomery , just published the v0.3 with the reporting of SDE versions added. Maybe also something useful to you. Looks like this:

versions_sde

@AlexArcPy Versions will be very helpful as well. Im going to schedule this for all of our geodatabases (have a couple dozen) as a quick administrative reference. v0.3 looks great!