Ability to set up relationships between a feature class and a table/view in another DB without having to impose SDE repository on the other DB (like a dynamic geocode of a table that is not “in” your geodatabase) I have trouble convincing DBAs from other departments/agencies to allow me to tinker with their existing DBs.It would be nice to create dynamic geocodes from a read only view of another database.
