As an aside, I'm pretty sure you won't want the amount to be FLOAT as this will not give exact results in calculations.

One other thing to be aware of is that EXCEPT eliminates duplicates.

You were asking how to do something and I was suggesting some ways of making it work. I don't see how that is belittling.

I don't think using the transaction name to determine which action to take is the right model. Your application already knows whether the user intends to insert, update or delete...

In your database, create a user-defined table type that matches the columns in "myorder". Your stored procedure can then specify a parameter that uses this table type instead of one...

Not an explanation of your problem, but in our warehouse we tend to drop indexes then truncate/load then recreate the indexes. It is generally a lot quicker on low-spec servers...

Regarding your 2nd question "should I worry about it", I'd say it's definitely worth giving them sensible names if you have copies of the database for development, QA, etc. and...

When you insert the copied rows...

Select DeveloperName, HitCount
from AppDevelopers
cross apply ufn_BigStick(AppDeveloperID)

GO 20

Why do you want to exclude the IDENTITY columns in the first place? If you use SET IDENTITY_INSERT <your table> ON you can copy the identity values across as well.

You can sum a nullable column. Rows where the column is null will not contribute to the total, so leaving the marks null when the student was absent (for whatever...

I'm assuming you can't use suser_name() or an equivalent because the application connects using a SQL Server login rather than windows authentication. You could prevent deletes, etc. from occurring outside...

I think the UserID variable in your code will be receiving the RETURN value from executing the stored procedure. This is not the same as the results of the SELECT...

Running multiple SQL statements passed in as a string.

This method looks highly vulnerable to SQL injection attacks.