Schema synchronization script failure during target environment update

Direct answer

DataGrip does not provide a built‑in way to automatically inject custom data‑transformation logic into the DDL it generates during schema synchronization. The tool creates a plain SQL script based on structural differences, and you must edit that script manually (or with an external migration framework) before running it if you need UPDATE, data‑copy, or transformation steps.

How to add custom logic

1. Open Tools → Compare → Databases (or the schema comparison dialog from the Database tool window).
2. Select your source and target connections, click Compare, and review the differences.
3. In the dialog’s Options tab, adjust what DDL is generated (e.g., uncheck Generate DROP statements to avoid destructive drops).
4. Click Generate Script. DataGrip opens the script in the SQL console.
5. Before executing, edit the script: add any required UPDATE, INSERT … SELECT, or temporary‑table steps that preserve data during column type changes, splits, or merges.
6. Run the edited script (or save it as a migration file for later use).

Prioritizing non‑destructive paths

To steer DataGrip toward safer, additive changes:

• Disable Generate DROP statements and Generate CREATE OR REPLACE options.
• Enable Use ALTER TABLE … ADD COLUMN (the default) and ensure Generate IF NOT EXISTS is checked for objects you want to create only if missing.
• If the target database supports it, turn on Generate temporary tables for data migration (available in recent DataGrip versions via the Advanced tab). This creates a staging table, copies data, alters the column, then moves data back—effectively non‑destructive.
• After generating the script, inspect it for any DROP or RECREATE statements and manually replace them with ALTER-based logic if needed.

When to ask for more detail

If you are already using a versioned migration tool (Flyway, Liquibase, etc.) and the schema sync script is being re‑applied despite a migration history table, let me know which tool and its version; that would change the recommendation to rely on that tool’s migration files instead of DataGrip’s generated script.