Not sure if that's the case or not, but while he complains about SQL Server's default locking strategies, it doesn't seem like he has tried running his queries

Not sure if that's the case or not, but while he complains about SQL Server's default locking strategies, it doesn't seem like he has tried running his queries using any non-default ones. In the end he goes with read comitted snapshot isolation level which I agree sounds like overkill and an unnecessary load on tempdb, but from reading his post, it seems he has honestly never heard of the SQL Server way of doing things trough setting and using regular transaction isolation levels, as opposed to the no lock hint he for MySQL and Oracle. I might be wrong, but to me this honestly seems like a case of not knowing your tool and how to use it properly.