none
Multiple clients to SQL Server database RRS feed

  • Question

  • This probably isn't the right forum for this but where can I find information on how to design an application with multiple clients (C#/.NET/LINQ/WPF) to a single SQL Server instance to avoid race conditions. I'm more interested in race conditions between a SELECT and UPDATE than anything else.

    For example, my clients will fetch a database record (with SELECT) and display it in a window (Yes, I'm not using data-aware components). If the user modifies the data in the window, it is saved back to the database (with an UPDATE). But what if another client also views this same record and also modifies it.  How do I prevent this from happening?  Is it a problem if it does happen? Are there other cases I should be concerned about?

    I'm aware of Isolation Levels but I don't think that is my solution.

    Thanks,

    Paul P.

    Saturday, July 14, 2012 1:48 AM

Answers