Manages Geodatabase workspace schema caches.
Product Availability
Available with ArcGIS Engine, ArcGIS Desktop, and ArcGIS Server.
Description
The schema cache is a cached snapshot of the geodatabase system tables (often referred to as the geodatabase schema). In an enterprise environment the geodatabase system tables (geodatabase schema) are in constant use by ArcGIS. Caching this schema locally can reduce database roundtrips by using the locally cached representation of the geodatabase schema.
Members
| Description | ||
|---|---|---|
 |
DisableAllSchemaCaches | Disable the schema caches of all open workspaces. |
|
DisableSchemaCache | Disable the schema cache for a specific workspace. |
|
DisableSchemaCaching | All new workspaces handed out by the factory will not have schema caching enabled. |
|
EnableAllSchemaCaches | Enable the schema caches of all open workspaces. |
|
EnableSchemaCache | Enable the schema cache for a specific workspace. |
|
EnableSchemaCaching | All new workspaces handed out by the factory will have schema caching enabled. |
|
IsAnySchemaCacheStale | Checks all current schema caches for staleness. |
|
IsSchemaCacheStale | Checks a specific schema cache for staleness. |
|
RefreshAllSchemaCaches | Refreshes all current schema caches. |
|
RefreshSchemaCache | Refreshes the schema cache for a specific workspace. |
CoClasses that implement IWorkspaceFactorySchemaCache
| CoClasses and Classes | Description |
|---|---|
| SdeWorkspaceFactory (esriDataSourcesGDB) | Esri SDE Workspace Factory. |
Remarks
It is most common to use the schema cache when the geodatabase schema is in heavy use. In ArcGIS this is most common when opening a large number of datasets. For instance internally, ArcGIS uses the schema cache when opening all the layers in a map document. The schema cache is most beneficial when working with large static data models where geodatabase objects like tables, fields, domains and relationships are well defined and do not change.
To get the greatest benefit from the schema cache the cache should be filled prior to opening any datasets. Once filled any calls to Open methods including IName.Open will be satisfied by the active schema cache and therefore optimized.