I just ran schema migration (update) and got all executed SQL logged to the SQL statement logger. So I am not sure what exact config option you have wrong, but clearly something. And since Spring is the thing configuring Hibernate, I can't say - I have no idea what Spring does here. Simplify your code to use just Hibernate and no Spring.

Alternatively you can set break-points and see exactly how Spring is configuring Hibernate given this Spring config. Start at org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator#process - what should happen is that you should end up with ActionGrouping with scriptAction=NONE and databaseAction=UPDATE. From there you should ultimately get into org.hibernate.tool.schema.internal.AbstractSchemaMigrator#doMigration and see the local variable targets initialized with GenerationTargetToDatabase.

Another option is to set the break point in org.hibernate.tool.schema.internal.exec.GenerationTargetToDatabase's implementation of #accept. When you hit that break point during schema-migration (you'll see AbstractSchemaMigrator in the call stack) you are at the right place (again, if not remove Spring).

Also, I'd make sure that logging.org.hibernate.SQL=DEBUG has the effect you think it does on the loggers.