I do use session per request but the updates are currently being done in a queue which has it's own session. The isolation level is IsolationLevel.ReadUncommitted.
To possibly clarify the issue, imagine throwing 100 updates at the database from 10 different requests in the space of a few seconds. Deadlocks are frequent. On Wed, Sep 1, 2010 at 10:14 PM, José F. Romaniello <[email protected]> wrote: > are you runing this command on a session per request? > what is the transaction scope ? > -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
