Due to edits, the adds and deletes table in an SDE geodatabase can grow quickly, which affects performance and can quickly bring normal operations to a standstill. The solution is to compress the geodatabase to remove the adds and deletes that are building up. The problem is if you have replicas set up, you must delete your replicas or else the tables that participate in those replias will not compress completely. Rebuilding replication is a pain. The child features must be completely deleted and recreated via a new replica, which means if there are any services, users, etc using those features, they must all be disconnected or stopped in order to perform a compress on the parent geodatabase. This means downtime.
Please provide a fix which will allow a compress to occur correctly with replicas in place.
