20260804173126

code/fms/fms-api/config/migrations/README.md

@@ -9,7 +9,20 @@ Run against a backed-up `FMS` database in this order:
 3. `verify_module_architecture.sql`
 
 `033` is a one-time transaction: it migrates valid metadata and removes the old metadata tables only after conversion checks pass. It intentionally does not create compatibility views or dual writes.
+If the earlier intermediate implementation created only `s_module_profile`, `s_function_node`, or `s_page_node`, `033` verifies that the complete source model still exists and regenerates those derived tables inside the same transaction. Other partial target states are rejected.
 
-`034` uses SQL Server `GO` batch separators because each `CREATE OR ALTER VIEW/TRIGGER` must start its batch. Use SSMS, Azure Data Studio, `sqlcmd`, or another runner that understands `GO`.
+`033` and `034` use SQL Server `GO` batch separators. Use SSMS, Azure Data Studio, `sqlcmd`, or another runner that understands `GO`.
 
 `verify_module_architecture.sql` is a target-schema verification script. It does not modify application tables.
+
+To check and conditionally apply `034` with the repository JDBC driver on Windows:
+
+```powershell
+$jdk = "D:\devtool\jdk\jdk-21\bin"
+$driver = "tools\migration\mssql-jdbc-13.4.0.jre11.jar"
+& "$jdk\javac.exe" -encoding UTF-8 -cp $driver -d $env:TEMP config\migrations\tools\ApplyModuleRuntimeViews.java
+& "$jdk\java.exe" -cp "$env:TEMP;$driver" ApplyModuleRuntimeViews
+```
+
+The tool refuses non-`FMS` catalogs and executes `034` only when a required runtime view is missing.
+For a database in the validated intermediate state, run `ApplyModuleRuntimeViews --dry-run-cutover` first. After verifying a database backup, `ApplyModuleRuntimeViews --apply-cutover` executes `033`, then conditionally executes `034` and verifies all required runtime views.