The following table shows which versions of ArcGIS for Desktop, ArcGIS Engine, and ArcGIS for Server Workgroup are compatible with which geodatabase releases:
Client release | Geodatabase release |
---|---|
10 | 10, 9.3.x, 9.2 |
10.1 | 10.2.x, 10.1, 10, 9.3.x |
10.2.x | 10.3, 10.2.x, 10.1, 10, 9.3.x |
10.3 | 10.3, 10.2.x, 10.1, 10 |
It is important to note that it is the release of the connecting client that determines the version of the geodatabase that is created. If you have a mix of client releases at your organization, there is the potential to have different release geodatabases on the same database server.
The following scenarios are possible when using mixed client releases with database servers:
- A newer client can create a newer release geodatabase on a database server that is licensed for an older version of ArcGIS. For example, a 10.3 client can create a 10.3 geodatabase on a database server that is licensed for 10.2.
- There is the potential for later release clients to upgrade the geodatabases created by earlier-release clients. That may or may not be acceptable for your workflow—you need to decide the rules your users must follow in regard to this functionality. As always, users should create a backup of the geodatabase before upgrading it.
See Compatibility between ArcGIS clients and geodatabases in SQL Server for general rules on interoperable connections to geodatabases.
You can check the Database Properties dialog box to see the release of a specific geodatabase. The Upgrade Status section on the General tab indicates the major and minor releases of the geodatabase.
Feedback on this topic?