Post and rec posts up -all- feature classes in a database, right?
Issue is, Differences Pane only shows the feature classes in that particular Pro project. I guess we could add all 500 feature classes to a Project?
I already posted this but to sum up, Esri can do a few things for versioning to be useful and safe to use.
1) allow child to child comparison and Differences pane review
2) allow accept / reject/ modify one by one or in batch (shift click or use SQL /select by location to whittle down changes to approve, reject, modify)
3) allow archiving on Child versions not just the Default
4) allow post and rec only for SOME feature classes in the SDE. Not all of them, as it appears is how it works. Additionally, a filter to only post and rec certain records and/or certain fields of certain records.
If Orgs have more than one version, unless you are very careful you can lose data. And of course you have to post and rec often; both to see edits and to compress. A recipe for error driven by operator fatigue (from doing so many times). I also don't trust this to be automated. Suffice to say, I think one of the main areas that has long needed attention is SDE. Folks will be doing SDE for a long time. Plethora of reasons not to put everything into the PostgreSQL data store. Also basic things have been issues forever that are easily solvable. Need to delete a database user? Can't. Need SQL Server Management Studio. At least, that I know of. You can create a db user but not delete. Alas, I'm not an admin even though I'm a dev; and I can't get on SSMS nor even ask for things to be done on it at least not easily. Basically a customer that does backend admin could provide a laundry list of SDE things. Many of which eat up a lot of our week. Replication for example. It can be updated. I just changed schema on a simple parent to child replication to back up the SDE and I tried the tech article outlining the Export Schema, Compare Schema and Import Schema tools when you right click on the SDE. It 'should' work. It didn't. So I have to re-create several replications for versions.
All this to say, I came to post a question to see if I SDE versioning was supposed to post all feaure classes at once regardless of what was in the Pro table of contents. Anyone else feeling me on SDE backend administration? I've been doing GIS sysadmin and dev for 13 years and things just seem to be increasingly complex but the same problems and challenges continue to exist.
