Similar to #33987 , with the update to Spring boot 3.4 nested transactions are also broken in SQL Server. Annoyingly SQL Server JDBC throws a com.microsoft.sqlserver.jdbc.SQLServerException rather than java.sql.SQLFeatureNotSupportedException so this isn't handled by the fix that went in for Oracle.
2025-01-10 01:01:13,380 DEBUG [tomcat-handler-493] o.s.jdbc.support.JdbcTransactionManager - Releasing transaction savepoint
2025-01-10 01:01:13,381 DEBUG [tomcat-handler-493] c.m.s.jdbc.internals.SQLServerException - *** SQLException: com.microsoft.sqlserver.jdbc.SQLServerException: This operation is not supported. This operation is not supported.
2025-01-10 01:01:13,381 DEBUG [tomcat-handler-493] o.s.jdbc.support.JdbcTransactionManager - Initiating transaction rollback
2025-01-10 01:01:13,381 DEBUG [tomcat-handler-493] o.s.jdbc.support.JdbcTransactionManager - Rolling back JDBC transaction on Connection [HikariProxyConnection@107047065 wrapping ConnectionID:1 ClientConnectionId: c741adb7-2049-48ae-ada2-37974c7dc396]
Similar to #33987 , with the update to Spring boot 3.4 nested transactions are also broken in SQL Server. Annoyingly SQL Server JDBC throws a
com.microsoft.sqlserver.jdbc.SQLServerExceptionrather thanjava.sql.SQLFeatureNotSupportedExceptionso this isn't handled by the fix that went in for Oracle.