Home/ Questions/Q 8279345
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-08T09:18:20+00:00

I would like to know more about the internal behavior of a sql_server. My

  • 0

I would like to know more about the internal behavior of a sql_server.

My problem is that I’m trying to create a multi-user data base but I’m experimenting concurrency data problems.

As an example:

  1. UserA opens an application and modifies something in the tableA without committing.
  2. UserB opens also the application and tries to read the tableA too.
  3. UserB is blocked until userA commits

My questions are:

  1. How can I resolve that?
  2. Isn’t there a way for giving the userB old information, letting him know that the information is old?
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    opens an aplication an modify something in the tableA without
    comitting

    Don’t write applications that do this. No application should hold locks for the duration of user actions. Editing a form should not lock the data. Read about Optimistic Concurency.

    Application will still block occasionaly and the best approach is to deploy row based versioning, aka. SNAPSHOT ISOLATION. See Understanding Row Versioning-Based Isolation Levels.

    • 0