797836 wrote:Yes, that's what they were designed for.
Yes for sure we can handle it using various Isolation levels or locking strategies.
But that will slow down the process?Yes. That's the price you have to pay. Is there an actual problem or are you just guessing?
Because when the locking is done on a particular resource until it is released the other user cannot do his operation.That depends entirely on the locking type.
Hence can slow down the process considerably.What is "considerably" in your opinion? What type of locking are you currently doing and how long are your transactions?
How we can handle concurrent users accessing the DB tables records and still go through with a better scalability and performance.Databases are very efficient in handling transactions concurrently. You sound like you're looking for a solution for a problem that doesn't exist.