thanks! yeah, you could do it in database too, but.. I don't use stored procs (at least not in this app); and my goal was to figure out proper actions from the client side while firing dumb SQLs, with many client threads - that's the model of the real world app I think.

Making SQLs/procs include extra stuff (especially Waits) to model concurrency - IMHO it's a distortion of the test case; and brings some doubts about final recipe - will it still work without WAITs and with 100 clients.

You know, your post is the first feedback I got so far. From any place - codeproject, LinkedIn, here, few other places. Looks like nobody cares about this stuff. That really really surprises me. Not that I feel the article is so good, but the subject?! Feel like I lost connection to this world, what's important and what's not.

thanks again for your interest!