Which is an example of a schema lock?
Schema locks, both shared and exclusive, apply to individual datasets and related tables in a file geodatabase. For example: If you acquire a lock on a feature class within a feature dataset, the lock applies to the entire feature dataset and its contents.
Where do I find schema lock in ArcGIS?
Users must have read/write access to the file geodatabase folder to make changes to its schema. Schema locks, both shared and exclusive, apply to individual datasets and related tables in a file geodatabase. For example:
When does ArcGIS automatically acquire a shared lock?
ArcGIS automatically acquires a shared lock on an individual dataset when it is in use, for example, anytime a user is editing or querying the contents of a feature class or table. This mechanism is used so other users cannot make changes to the underlying dataset and its schema while it is in use.
When to use ArcGIS to change geodatabase schema?
Any number of shared locks can be established on a single feature class or table at any given time. When you use ArcGIS to modify your geodatabase schema—for example, to add a field or alter rules—ArcGIS attempts to establish an exclusive lock on the data being altered.
How are schema changes made in a geodatabase?
In addition, schema changes are made to existing datasets—to add an attribute column, change the rules in a topology, add cartographic representations, and so forth. If you are working with a single-user geodatabase, these changes are easy to make, and you do not have to think about how your work might impact others.
When does a lock apply to a geodatabase?
In personal geodatabases, all locks apply to all the contents in the whole geodatabase. Once an exclusive lock or a shared lock is acquired on an item in a personal geodatabase, that lock applies to the entire geodatabase. This means that only one editor can edit a personal geodatabase at a time.