I'm doing some research on creating a new field in my SQL Enterprise Geodatabase. Can I add a new field while I have existing versions? Or would I need to roll everything up before I add the field that way I don't lose any edits?
The research I have found says both are possible. Can anyone verify what is best practice?
Any info is helpful.
You can add a new field, even when you have multiple versions. That won't be an issue.
Check this article: Versioning 101 - Essential information about ArcSDE geodatabases
Edits that are made within a version are isolated to that version until its owner or the ArcSDE administrator decides to merge the changes into another version. The exception to this statement is schema changes. When the schema in a version is changed—for example, by adding a new field to a table—the change applies to all other versions.
If the Feature Class is participating in a Replica, then you need to take care of that. Working with schema changes