I would like to know the best approach.
I have 10 different screens accessing the same table for an unique order number. Once a screen requests a unique number the same is generated and stored in this table and this value is sent back to the screen. This becomes a problem when the requests are concurrent. We had used table level locks for this purpose. Is there a better approach like request/message/thread queuing so that only one access happens at any point of time and other requests are queued up and serviced async?