diff --git a/modules/ROOT/pages/database-internals/store-formats.adoc b/modules/ROOT/pages/database-internals/store-formats.adoc index 664b6a65b..48ef518c8 100644 --- a/modules/ROOT/pages/database-internals/store-formats.adoc +++ b/modules/ROOT/pages/database-internals/store-formats.adoc @@ -118,12 +118,19 @@ bin/neo4j-admin database copy --to-format="block" mydb blockdb CREATE DATABASE blockdb OPTIONS {storeFormat: 'block'} ---- - [[change-store-format]] === Changing the store format of existing databases -Starting from 5.23, `block` format is the preferred format for Enterprise Edition due to its superior performance and scalability. -Therefore, migrating all databases to `block` format is recommended to ensure optimal performance. +Starting from 5.23, `block` format is the recommended format for Enterprise Edition due to its superior performance and scalability. +It uses advanced data structures and inlining techniques to enhance data locality, which leads to better resource utilization. +Therefore, it is highly recommended that Enterprise Edition users migrate all databases to `block` format at their earliest convenience to ensure the best possible performance. +`block` format is the default format for new databases created in 5.23 and later, and is the default format for all databases in 5.26 and later. + +From 5.25 onwards, the `block` format supports token names (including node labels, property keys, and relationship type names) of any length up to the GQL identifier max length of 16,383 characters. +Thus, token names must adhere to this length limit when migrating from `aligned` to `block` format. + +`standard` and `high_limit` formats are deprecated in 5.23 and will be removed in a future release. +For more information, see <>. [NOTE] ====