Hi thank you so much for these information!
I think we would be allowed to make the database do concurrency for us, how is this achieved?
Unfortunately I'm not a Database Admin, so I don't know how to configure it to do that for you. I typically rely on the ORM I use (Entity Framework or nHibernate) to sort that out for me, or roll my own using a pattern I gave above. This link looks useful though
And could we just like, create a hashmap within the server's memory that would contain a list of user's and the corresponding tables they are using during the system's run? There a lot of tables for the database as of the moment and, I am guessing that your methodology can be achieved through this with the same effect? Please correct me though if I sound wrong and obnoxious.
Sure, if you want to lock the entire table. I don't think this would be a good idea and leads to deadlock more readily. But this may be a requirement of your software. How you do it is up to you, just pick what is appropriate for your requirements.
Speaking of deadlock, this is something you need to approach very carefully and test rigorously. Although I'm sure you'll know what deadlock is, I'll explain just in case. It is when one part of a program holding a resource is waiting for another part of the program to release a different …