When I access a feature class in an Enterprise Geodatabase that is not registered as versioned – will the version tree and state tree effect performance?
Our PROD database is 99% simple read only feature classes. There are one or two feature classes that are registered as versioned. We are considering placing the versioned data into a user-schema geodatabase with the thought that it would make compress back to state zero easier, and thus make management of the instance more efficient. Ie we would not have to kick all the users off the database to do a successful compress back to state zero – just the schema user.
… or are we overthinking this?