We are currently editing a one-to-many relationship (setup in ArcMap) between geospatial data and a non-spatial table (both within the same enterprise geodatabase). Though, I believe we may be lacking "referential integrity", because we have orphans within the table. I was looking at the online documentation here:
- Would a relationship class setup in the geodatabase solve our problem with orphans?
- Would database versioning have an affect on the relationship class? If so, how?
- Are Global IDs necessary in an enterprise Geodatabase for a relationship class?
Any help would be appreciated.