![arcmap versions arcmap versions](https://i.stack.imgur.com/zMNAT.png)
Use supported versions of ArcGIS for your clients and geodatabase.The following rules apply for compatibility:
![arcmap versions arcmap versions](https://desktop.arcgis.com/fr/arcmap/latest/map/working-with-arcmap/GUID-64F8F06A-9895-4071-B261-75B8E922F2BE-web.png)
The version for file geodatabases has not changed since 10.1.
ARCMAP VERSIONS UPGRADE
Be aware that this geodatabase version is primarily used by Esri Support to troubleshoot issues it does not entirely reflect the functionality available to you, as a lot of geodatabase functionality is implemented in the clients that access the geodatabase and not in the geodatabase itself.įor enterprise geodatabases, the geodatabase version mostly only reflects what software version you used to create or upgrade the geodatabase. If you subsequently upgrade the same geodatabase using ArcGIS Pro 2.6, the geodatabase version is 10.8.1.2.6.
![arcmap versions arcmap versions](https://i.ytimg.com/vi/am9I3WJFakk/hqdefault.jpg)
For example, if you create an enterprise geodatabase from ArcMap 10.6.1, the geodatabase version is 10.6.1. It indicates what client version you used to create or upgrade the geodatabase. The geodatabase version for an enterprise geodatabase is stored in a system table. For enterprise geodatabases, waiting too long between geodatabase upgrades may mean you have to upgrade the underlying database more than once before you can upgrade the geodatabase. A newer client can create newer dataset types in the geodatabase that older clients cannot access. This is especially true when you use a mix of client versions at your site. If you let one get too many releases awayįrom the other, you risk encountering problems or unexpected behavior. Geodatabases and client software are designed to work together, and You do not have to keep your geodatabase and ArcGIS clients at the same release, but it is recommended that you do so.