Are there any consequences (geodatabase performance or other) to having domains "stack up" in a SQL Server-based SDE geodatabase? I noticed many unused domains in an SDE workspace when running a script that writes domain properties to a series of file geodatabase tables. The script is attached. A lot of them have the same base name followed by an underscore and then a number:
In this particular enterprise geodatabase, there are 913 domains but only 93 of them are actually applied. So, is this ok? Or is there a compelling reason to clean up the unused domains and try to prevent them stacking up like this in the future.