Does Esri have any specific plans for maturing geodatabase design? Especially for VLGDBs (Very Large Geodatabases)--large with respect to the number of objects--that need to integrate with the Enterprise.
Seems there's no sense of urgency to move GDB design toward parity with modern relational database design. If there's insufficient customer demand, that's one explanation--it's tough to deploy resources toward something few people explicitly say they want. If there is demand, it's probably challenging to provide a solution that would satisfy the largest possible base of geodatabase modelers.
I'm open and interested in any good solution that steers the geodatabase modeling and design community away from ad hoc work, disconnected from requirements and the larger sphere of Enterprise IT. Doesn't have to be UML-based, but what are the alternatives?
Mostly, I'd like to see open and engaged conversation on this issue wherever it ultimately leads.