What is the difference between creating a geodatabase version and creating a dataset version?

[KevinWarnerTLN]

What is the difference between creating a geodatabase version and creating a dataset version? I have one geodatabase version (DEFAULT). When I check the box to enable versioning of a dataset in the geodatabase (and choose, for example, Traditional),

there is no new version that appears on the Manage Versions screen.

What is being created when I version a dataset, and where is this version information stored? How is it different from a geodatabase version?

[RobertKrisher · Accepted solution]

When you checked the "Versioning" box on the feature dataset, what you are doing is enabling the contents of that feature dataset (and any related objects) to be edited using the versioning tools and workflows. This means that all edits to these classes made while editing a version will remain isolated to that version until they are reconciled and posted with the default version.

To actually create a version, click the "New" button on the versioning toolbar (or in the manage version dialogs you have open). To edit features using that version you add the layers to your map and use the versioning toolbar (or the list by data sources tab) to change the active version to the version you created. Once you are done editing you can use the versioning toolbar to "Show Version Differences" or reconcile and post your changes.

Traditional versioning is very similar (in terms of workflow), but it is not supported for editing through web applications. Here is a collection of resources that talk about branch versioning:

• Getting to know Branch Versioning
• To Branch or Not to Branch
• Branch Versioning: Setting the Stage
• Editing and Administration with Branch Versioning - It's Showtime!
• QA/QC workflow with branch versioned data
• Manage Your Branch Versions with ArcGIS Experience Builder
• Version Management with ArcGIS
• Version administrator for branch versioned data