When you are upgrading to DXP on SQL Server, it is recommended to set the following property in the portal-upgrade-ext.properties file:

verify.process.concurrency.threshold=10000

Otherwise you can encounter issues during the upgrade related to schema changes after cursor opens, etc.

This can hit you during the verification of audited models or resource permissions, especially when you have large row counts.

The property setting above should make the verify processes run sequentially rather than in parallel and will prevent the kinds of exceptions like:

Caused by: java.lang.Exception: Verification error: com.liferay.portal.verify.VerifyResourcePermissions
	at com.liferay.portal.verify.VerifyProcess.doVerify(VerifyProcess.java:124)
	at com.liferay.portal.verify.VerifyResourcePermissions.verify(VerifyResourcePermissions.java:76)
	at com.liferay.portal.verify.VerifyResourcePermissions.doVerify(VerifyResourcePermissions.java:88)
	at com.liferay.portal.verify.VerifyProcess.verify(VerifyProcess.java:72)
	... 15 more
Caused by: java.util.concurrent.ExecutionException: com.microsoft.sqlserver.jdbc.SQLServerException: Could not complete cursor operation because the table schema changed after the cursor was declared.
	at java.util.concurrent.FutureTask.report(FutureTask.java:122)
	at java.util.concurrent.FutureTask.get(FutureTask.java:192)
	at com.liferay.petra.function.UnsafeConsumer.accept(UnsafeConsumer.java:42)
	at com.liferay.petra.function.UnsafeConsumer.accept(UnsafeConsumer.java:30)
	at com.liferay.portal.verify.VerifyProcess.doVerify(VerifyProcess.java:117)
	... 18 more