During migration jobs, particularly those involving large amount of data, the user experiences errors that the job terminated due to not being able to read from the source or target SharePoint site. The term "timeout" is often mentioned. Below is an example of a SQL Server Timeout:
Exception thrown: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun( ...
This is often caused by resources, which can either be the network, the memory usage on the server or the SQL Server itself.
One way to facilitate the migration jobs in an over-taxed resource environment is to increase the allowed timeout settings for accessing the SharePoint data.
Note: There may be a need to experiment and increase the setting/s gradually.