OK> I think, despite that the stored procedure inserts all data in one
OK> transaction, the trigger runs before the other records were inserted.

I am probably not the right person to dare such a statement, but isn't that as it should be, at least if your transaction is reading only committed versions?

Your trigger runs when the records have been inserted, but the insert is not yet committed.

It is possible to configure transactions to read uncommitted inserts, but that would be by far too hot to handle for me :)


---