>>I'd
>>-Check table headers
>>-Collect team and discuss why we are using buffering+transactions etc.
>>Cetin
>
>That's the concept we're all using here. I don't see what's wrong with it. We need to either save all the changes at once or reject them all.
>
>Anyway, I still didn't get how and where should I move API declaration to not affect anything. The GUID() still should be a stored procedure. The DBC events looked like a logical place, but for some reason it didn't work.

What's wrong with it? Test combinations and rethink why you need them both.
I don't understand your insistance GUID should be an SP. Do however you want.
Cetin