I have to move on. This seems like a major SQL bug, and since I have the stored Proc, I can't spend any more time on it.


I have no problem with this simple use of Instead Of Insert Trigger into the a view.

I can put 1000 rows into the view,
the trigger can split the view,
generate the 1000 new identities
and fill the 1000 dependant row correctly.

No bugs.

If you want use SCOPE_IDENTITY( ) for a complex triggers path, then problems occurs.

Fabio