Pretty senior developer here (manager now, actually) but I'm realizing that other than college, I haven't really picked up a book on SQL. What would you recommend?
https://learn.microsoft.com/en-us/sql/relational-databases/s.... Explains that SQL Server handles the problem of two concurrent users attempting to modify the same record at the same time via DEADLOCKS. You want to use Extended Events to troubleshoot deadlocks.
https://www.business-case-analysis.com/accounting-cycle.html. I would argue the best architecture to minimize deadlocks is to mimic what accounting systems do. Multiple Clients submit order requests to a batch system that posts/processes them sequentially. Until the central batch system posts, the transaction is pending. Similar to how Amazon accepts your order request instantaneously; but it may take several minutes for your order to be confirmed.
Point of clarification: I've used SQL almost my entire development career, with multiple RDBMS engines, I've simply never looked at a book solely on SQL.
Just go through the W3Schools website first. It's free and you can write queries in the little window to test out things against their simple database.
