You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Neo4j 2025.02, an additional option is added to the recreate procedure.
366
-
The new option `clearData` deletes the data (e.g., nodes and relationships) and the schema (e.g., constraints and indexes) for the database.
367
-
This means you end up with an empty store, but as with the other recreate database options, all privileges associated with the database are kept.
368
364
369
-
When, and only when, the clear data option is used, the store format can also be changed for the recreated database.
370
-
See xref:database-internals/store-formats.adoc[Store formats], for more details about available database store formats in Neo4j.
371
-
If the store format option is not defined, the recreated database ends up with the same store format as before the recreation.
365
+
[[alter-topology-recreate]]
366
+
=== Change the topology
372
367
368
+
There is an option to define a new topology when recreating a database.
369
+
This can be beneficial during a disaster, if enough servers are not available to recreate the database with the original topology.
370
+
When altering the total number of allocations down during a recreation, it is important to remember that the number of seeding servers cannot exceed the number of total allocations of the database.
371
+
This also holds true when using recreate with an empty list of seeders.
372
+
If there are more available servers in the cluster hosting the database than the number of new allocations, the recreation will fail.
In Neo4j 2025.02, the `clearData` option was added to the recreate procedure.
385
+
This option allows you to delete the data (e.g., nodes and relationships) and the schema (e.g., constraints and indexes) for the database.
386
+
This means you end up with an empty store, but as with the other recreate database options, all privileges associated with the database are kept.
387
+
379
388
[CAUTION]
380
389
====
381
390
Using the clear data option means the data and schema will be deleted *permanently*.
382
391
If you want to have the option of getting them back later, make sure to take a backup before clearing the database.
383
392
See xref:backup-restore/online-backup.adoc[Online backup] for more information.
384
393
====
385
394
386
-
[[alter-topology-recreate]]
387
-
=== Change the topology
395
+
[role=label--new-2025.04]
396
+
[[alter-store-format]]
397
+
==== Alter the database store format
388
398
389
-
There is an option to define a new topology when recreating a database.
390
-
This can be beneficial during a disaster, if enough servers are not available to recreate the database with the original topology.
391
-
When altering the total number of allocations down during a recreation, it is important to remember that the number of seeding servers cannot exceed the number of total allocations of the database.
392
-
This also holds true when using recreate with an empty list of seeders.
393
-
If there are more available servers in the cluster hosting the database than the number of new allocations, the recreation will fail.
399
+
In Neo4j 2025.04, the database store format can also be altered during recreation, but only when the `clearData` option is specified.
400
+
This functionality is available through the new `dbms.recreateDatabase()` procedure.
401
+
402
+
See xref:database-internals/store-formats.adoc[Store formats], for more details about available database store formats in Neo4j.
403
+
If the store format option is not defined, the recreated database ends up with the same store format as before the recreation.
0 commit comments