diff --git a/Spring-Batch-5.0-Migration-Guide.md b/Spring-Batch-5.0-Migration-Guide.md
index 0e960f4..ea0b8f0 100644
--- a/Spring-Batch-5.0-Migration-Guide.md
+++ b/Spring-Batch-5.0-Migration-Guide.md
@@ -17,8 +17,9 @@ Spring Batch 5 is updating its Spring dependencies across the board to the follo
 * Spring Data 3
 * Spring AMQP 3
 * Spring for Apache Kafka 3
+* Micrometer 2
 
-## DDL scripts updates
+## Database schema updates
 
 #### Oracle
 
@@ -36,6 +37,16 @@ CREATE SEQUENCE BATCH_JOB_SEQ START WITH 0 MINVALUE 0 MAXVALUE 92233720368547758
 
 New applications can use the provided script with no modifications. Existing applications should consider modifying the snippet above to start sequences from the last value in sequence tables used with v4.
 
+#### All platforms
+
+The column `JOB_CONFIGURATION_LOCATION` in the `BATCH_JOB_EXECUTION` table is not used anymore and can be marked as unused or dropped if needed:
+
+```
+ALTER TABLE BATCH_JOB_EXECUTION DROP COLUMN JOB_CONFIGURATION_LOCATION;
+```
+
+The syntax to drop the column might differ depending on the version of your database server, so please check the syntax of column deletion. This change might require a table reorganisation on some platforms.
+
 ## Job repository/explorer configuration updates
 
 The Map-based job repository/explorer implementation were deprecated in v4 and completely removed in v5. You should use the Jdbc-based implementation instead. Unless you are using a custom Job repository/explorer implementation, the `@EnableBatchProcessing` annotation will configure a Jdbc-based `JobRepository` which requires a `DataSource` bean in the application context. The `DataSource` bean could refer to an embedded database like H2, HSQL, etc to work with an in-memory job repository.