Does anyone know how many related tables can be associated with one feature class in an enterprise geodatabase? Is there a limit or a suggested limit, based on performance? Thanks!
Are you referring to Composite relationships (related tables are maintained by relationship) or just simple ones? My guess would be that simple relationships don't affect performance.
Good question, all of our related tables are simple relationships. I didn't think so either, but I have not found any documentation on it so I figured I'd ask. Thanks.
