Skip To Content

Considerations for Neo4j databases used as NoSQL data stores

If you are using Neo4j databases as NoSQL data stores that are registered with your ArcGIS Knowledge site, there are some details to consider to ensure your knowledge graphs operate correctly. For example, you must create a coordinated back up and restore plan that synchronizes backups of your Neo4j databases, your ArcGIS Data Store graph store, and your ArcGIS Enterprise deployment.

Create a knowledge graph

The first step in using a Neo4j database with your ArcGIS Knowledge site is to create a Neo4j database using Neo4j administration commands. Register the new, empty database with your site as a NoSQL data store. If you attempt to create a knowledge graph using a Neo4j database that isn't completely empty, the operation will fail.

When a Neo4j database is registered as a NoSQL data store, it can be registered using either the database name or an alias assigned to it. The name or alias you use is subject to the same naming restrictions as the knowledge graph. Once the NoSQL data store has been created, the database can't be renamed or the alias can't be changed or dropped in Neo4j.

Edit data in ArcGIS only

The graph store associated with your ArcGIS Knowledge site stores schema information that must be kept in sync with the entities and relationships stored in the Neo4j databases associated with your site. The graph store also stores all spatial data associated with entities and relationships in the knowledge graph. Global identifiers are defined for each graph item in the knowledge graph, and these identifiers must be kept in sync in all three systems for the knowledge graph to remain operational.

To ensure data integrity, edits to all systems associated with a knowledge graph, including associated Neo4j databases, are only supported through operations and requests made to the knowledge graph in ArcGIS Pro and ArcGIS Enterprise. Edits to the Neo4j databases must not be made from outside ArcGIS.

Delete the database

When you no longer need a knowledge graph, you can delete it in the Enterprise portal. Data for the knowledge graph is deleted automatically from the graph store. However, if the knowledge graph references a NoSQL data store, the data store and its associated Neo4j database are not deleted automatically. You can't create a knowledge graph using the same NoSQL data store and Neo4j database.

Before you delete the NoSQL data store in the Enterprise portal, check its settings and make note of which Neo4j database it references. You can then take steps to archive the data and delete the Neo4j database using Neo4j utilities and administration commands.


Once a knowledge graph has been deleted from the Enterprise portal, you can't use any investigations stored in your ArcGIS Pro projects. An existing investigation can't be associated with a different knowledge graph. You will have to delete investigations that reference the deleted knowledge graph from all projects where they exist or delete the projects themselves, as appropriate.