So, after more tests, it seems that the issue arises if the feature class is not organically created in the sde database. If you create the layer based on an imported shapefile, the indicator count issue seems to be incorrect.
However, the issue was resolved after copying the data from the current sde database to another sde database, and then importing it back into the original sde database (as a new layer).
Contrary to my previous post, it seems like the database platform was not really the issue. Copying the feature class out and bringing it back in seemed to reset the schema and it also avoided the strange bugs that occurred previously. You should give that a try and see if it works since it did for us.