I guess the table scan is seqid from db2. Strange that is isn't an index scan. Is that the table or is that the one of the top-clusterindex scan
The not-in isn't really sargable which explains the clustered index scan on db1 (as you need the other columns in case it matches)