Unregister As Versioned (Data Management Tools)
Summary
Unregisters an enterprise geodatabase dataset as versioned.
Usage
The input dataset must be from a database connection established as the data owner.
An exclusive lock is required on the dataset.
Unregistering a branch versioned dataset without first posting all named versions to the default version may result in a loss of edits.
Unregistering a traditional versioned dataset without first compressing the geodatabase may lead to loss of edited data.
Parameters
| Label | Explanation | Data type |
|---|---|---|
|
Input Dataset |
The name of the dataset to be unregistered as versioned. |
Table View; Feature Dataset |
|
Do not run if there are versions with edits (Optional) |
Specifies whether edits made to the versioned data will be maintained.
|
Boolean |
|
Compress all edits in the Default version into the base table (Optional) |
Specifies whether edits will be compressed and unused data will be removed. This option is ignored if the Do not run if there are versions with edits parameter is checked. This parameter is only applicable for traditional versioned datasets.
|
Boolean |
Derived output
| Label | Explanation | Data type |
|---|---|---|
|
Unregistered Dataset |
The unregistered dataset. |
Table View; Feature Dataset |
Environments
Licensing information
- Basic: No
- Standard: Yes
- Advanced: Yes
Related topics
- An overview of the Versions toolset
- Find a geoprocessing tool
- Overview of versioning
- Versioning types
- Versioning tab
- Branch version scenarios
- Traditional version scenarios
- Register a dataset as branch versioned
- Connect to a branch version
- Register a dataset as traditional versioned
- Connect to a traditional version