Dear colleagues!

Usually we using @@IDENTITY in our projects to get ID of latest inserted record. in 95% it works perfect. But today our team found very serious bug, what appears with @@IDENTITY. Our team is developers of Universal List - The Easy Forms & Application Builder for DNN This module allows to save owners of records (owner and last user, who changed record) and usually for it we used @@IDENTITY. But yesterday we recieved request from our client. He said that owners detected in worng way, and for example instead ID=200 he received strange numbers like ID=18123. We spent some time on this problem and found next situation: Client using Triggers for DNN table (as we know, usually DotNetNuke users do not use triggers). @@IDENTITY do not working correctly with triggers and need to use other SCOPE_IDENTITY()

So may be you have (or had) same problem - it can help you.

Please write us if you have any questions.

As long as I remember, DNN uses SCOPE_IDENTITY().

I also use this function for my own modules.

Also, you must be sure how many tables are u updating at this stored procedure and if more than one table, you need to make you what value is this function returning. Typically this function will return the last updated identity.