The only difference between executions is the data content of fields, the statement is always the same.

Possible, we will try that although anytime we submit SQL statements with compilation errors in them we get them logged in our log and we fixed all of those issues...

That is correct, the functions I sent you are executed about 12,000-18,000 times per day and work fine 99.9999% of the time. As I described before, the above code...

Below is our VB.NET code that we use to insert reservations into the XDispTrips table. Let me know if you would rather see an actual INSERT statement after it...

we will try that, thank you much...

Yes, 2008 R2...

Yes, we were going to try SCOPE_IDENTITY but sounds like that will not make any difference since we see gaps.

ALso was going to try the trace again - it is...

Thank you all very much, we will try a couple things that were suggested to see if we can figure this out...

Thank you all very much, we will take several of the suggestions and try them out to see if we can nail this down.

We do not have any triggers on the table that we are having issues with. We also have researched the logged identity for "disappearing" records and they are in...

The insert is done with an INSERT statement immediately followed by SELECT @@IDENTITY. Since it is a rare occurence (about 10 times per day) our theory has been that...