I have to create a File Geodatabase copy of my SDE Geodatabase to either use as backup or send to another organization periodically. It's easy to do in Catalog, I can simply drag and drop each dataset into a newly created FGDB and everything will load, attachment tables, relates, and domains. However I don't want to do this manually and would prefer to do it programmatically. So I want to see how the UI does it under the hood, so to speak as I don't know all the processes it takes to get it right. But there's no reference to the geoprocesses that occur and naturally, of course, there's nothing I can export to see the multiple steps it takes to properly copy and coordinate the operation through it's chosen scripts operating behind the scenes.
So my suggestion is to make these UI processes transparent and exportable to python or, even better, model builder to get a script so I can reference and learn from in my own Python self-education.
I think many desktop users would find value in referencing this operation and emulating its processes in script so we can, not only conduct simple copies of the FCs, but to make sure all the associations, domains, attachments etc. are accounted for in the replicated FGDB.
I think this is what the Copy Tool does. I have always considered it as the arcpy equivalent of copy/paste
Yeah, well with SDE and a file geodatabase transfer won't work with this geoprocess as they are two different workspaces. I'm looking at copying to an XML workspace that could be a workaround. Ideally it would be nice to have what the UI is doing in some kind of logged description.
So the UI operations (dragging and dropping datasets into the new FGDB) that work behind the scenes have some kind of conditionals to check each FC to see what associations as well as acknowledge and copy the names of the dataset and their included layers. I'd like to know how it avoids the workspace confliction - hence the request to be able to export its operations into a ModelBuilder script or .py export - or even just some output of a pseudocode would be fine.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.