>>>That's because I like to play a host to my code :). Surely, I have a class which has a method which hosts this code.
>>
>>Does it handle even a SQL Server case of this same issue ?
>
>No, SQL Server has inherent HOLDLOCK and nothing else. Also, there is Identity property to provide unique ID w\out troubles.

Then, could I execute a server-stored procedure to lock the table or to create the Id and then pass it back to my update code ?