Database management command syntax
Almost all administration commands have variations. The most common variations include parts of the commands that are optional, or that can have multiple values. Some variations are indicated using special characters. See Reading the administration commands syntax for details.
This page summarizes the various command syntax options. It also includes examples for both Cypher 5 and Cypher 25 when available.
Cypher® versionsIntroduced in 2025.06
As of Neo4j 2025.06, the Cypher language is decoupled from the Neo4j server and follows its own versioning.
Currently, there are two versions of Cypher available: Cypher 5 and Cypher 25.
You can specify the version of Cypher by configuring a default Cypher version for the whole DBMS by explicitely setting db.query.default_language configuration in the neo4j.conf file, per database when using CREATE DATABASE or ALTER DATABASE, or by prepending the query with CYPHER 5 or CYPHER 25 on a per-query basis to override the default.
For more information, see the Configure the Cypher default version and Cypher Manual → Select Cypher version.
- Cypher 5
-
Cypher 5 is the language version with which all queries written for Neo4j 2025.05 and earlier versions are compatible. However, as of Neo4j 2025.06, it is frozen and will only receive performance enhancements and bug fixes in future server releases.
Setting the default language toCYPHER 5ensures that all queries run on that database use the version ofCypher 5as it existed at the time of the Neo4j 2025.06 release (unless you prepend your queries withCYPHER 25, which overrides this default). Any changes introduced after the 2025.06 release do not affect the semantics of the query.
Cypher 5 remains the default version for all newly created databases unlessdb.query.default_language=CYPHER_25is explicitly set on the DBMS level or overridden usingCREATE DATABASEorALTER DATABASE, or by prepending queries withCYPHER 25. - Cypher 25
-
Cypher 25 builds upon Cypher 5 and includes new and improved features, as well as some removals. Any new Cypher features introduced in Neo4j 2025.06 or later are added only to Cypher 25. Setting the default language to
CYPHER 25ensures that all queries run on that database use the version ofCypher 25that the database is currently running (unless you prepend your queries withCYPHER 5, which overrides this default). For example, a Neo4j 2025.10 database with default languageCypher 25will useCypher 25as it exists in Neo4j 2025.10, including any changes introduced in Neo4j 2025.06, 2025.07, 2025.08, and 2025.09.Starting from Neo4j 2026.02,the distributed neo4j.conf explicitly sets
db.query.default_language=CYPHER_25. As a result, new deployments using the provided configuration file default to Cypher 25 for newly created databases. The Cypher version can still be explicitly specified in theCREATE DATABASEcommand or can be changed at any time usingALTER DATABASE.If you want to use Cypher 5 as the default for new databases, you can remove or comment out that configuration entry, which is equivalent to setting
db.query.default_language=CYPHER_5. Existing databases retain their existing default language.
Reading the administration commands syntax
| Character | Meaning | Example |
|---|---|---|
|
Used to indicate alternative parts of a command (i.e. |
If the syntax needs to specify either a name or |
|
Used to group parts of the command. Commonly found together with |
In order to use the |
|
Used to indicate an optional part of the command. It also groups alternatives together, when there can be either of the alternatives or nothing. |
If a keyword in the syntax can either be in singular or plural, you can indicate that the |
|
Repeated pattern. Related to the command part immediately before this is repeated. |
A comma separated list of names would be |
|
When a special character is part of the syntax itself, surround it with |
To include |
The special characters in the table above are the only ones that need to be escaped using " in the syntax summaries.
Here is an example that uses all the special characters.
It grants the READ privilege:
GRANT READ
"{" { * | property[, ...] } "}"
ON {HOME GRAPH | GRAPH[S] { * | name[, ...] }}
[ ELEMENT[S] { * | label-or-rel-type[, ...] }
| NODE[S] { * | label[, ...] }
| RELATIONSHIP[S] { * | rel-type[, ...] }]
TO role[, ...]
Note that this command includes { and } in the syntax, and between them there can be a grouping of properties or the character *.
It also has multiple optional parts, including the entity part of the command which is the grouping following the graph name.
For details about the graph privilege commands syntax, see Components of the graph privilege commands.
However, there is no need to escape any characters when creating a constraint for a node property.
This is because ( and ) are not special characters, and [ and ] indicate that the constraint name and the IF NOT EXISTS parts are optional, and therefore not part of the command.
CREATE CONSTRAINT [constraint_name] [IF NOT EXISTS]
FOR (n:LabelName)
REQUIRE n.propertyName IS NOT NULL
Database management command syntax
The database management commands are used to manage standard or composite databases.
Show databases
| Command | Syntax |
|---|---|
|
|
Create a database
| Command | Syntax |
|---|---|
|
|
|
|
| Command | Syntax |
|---|---|
|
|
|
|
Create a composite database
| Command | Syntax |
|---|---|
|
|
|
|
| Command | Syntax |
|---|---|
|
|
|
|
Create a sharded property databaseIntroduced in 2025.12
| Command | Syntax |
|---|---|
|
|
When creating a sharded property database, the following are created:
-
A virtual sharded property database
<name>. -
A single graph shard with the name
<name>-g000. -
A number of property shards with the name
<name>-p<index>, where<index>ranges from000to999. The count property inSET PROPERTY SHARDSspecifies the number of property shards.
|
The
|
Alter a database
| Command | Syntax |
|---|---|
|
|
|
There can be multiple
|
Alter a composite databaseIntroduced in 2025.06
| Command | Syntax |
|---|---|
|
|
Alter a sharded property databaseIntroduced in 2025.12
| Command | Syntax |
|---|---|
|
|
|
|
|
|
Database alias management command syntax
The database alias management commands are used to manage local or remote database aliases.
Show aliases
| Command | Syntax |
|---|---|
|
Lists both local and remote database aliases, optionally filtered on the alias name. |
Create a local alias
| Command | Syntax |
|---|---|
|
|
Create a remote alias
| Command | Syntax |
|---|---|
|
|
|
|
| Command | Syntax |
|---|---|
|
|
|
|
Alter a local alias
| Command | Syntax |
|---|---|
|
|
Alter a remote alias
| Command | Syntax |
|---|---|
|
|
|
|