• Thanks for the suggestion, but pretty much the same result

    Are there any other tools I can use to dig deeper?

    Table '#Result____00000005022E'. Scan count 0, logical reads 51, physical reads 0, read-ahead reads 0, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0.

    Table '#Carriers______00000005022B'. Scan count 0, logical reads 170, physical reads 1, read-ahead reads 0, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0.

    Table '#Commodities____00000005022A'. Scan count 0, logical reads 1066, physical reads 1, read-ahead reads 0, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0.

    Table '#Cons____00000005022C'. Scan count 0, logical reads 3366, physical reads 1, read-ahead reads 0, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0.

    Table '#Incoterms____00000005022D'. Scan count 0, logical reads 13464, physical reads 1, read-ahead reads 0, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0.

    Table 'Worktable'. Scan count 0, logical reads 0, physical reads 0, read-ahead reads 0, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0.

    Table 'BRFCLSeaWeekHis'. Scan count 1, logical reads 778057, physical reads 1, read-ahead reads 775951, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0.

    Table '#TradeLanes____000000050229'. Scan count 1, logical reads 2, physical reads 0, read-ahead reads 0, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0.

    SQL Server Execution Times:

    CPU time = 36410 ms, elapsed time = 73626 ms.