Like Oracle, READ COMMITTED is the default transaction isolation setting for Microsoft SQL so if this is the problem, it is because they strangely changed the default.
FYI, for data warehouse work, MySQL does pretty darn well if you relax the transaction isolation level. By default, InnoDB uses a stronger transaction isolation than either Oracle or Microsoft. You can change it with this command:
SET TRANSACTION ISOLATION LEVEL READ COMMITTED
InnoDB defaults to REPEATABLE READ which while very nice (and nicer than Oracle's READ COMMITTED), but it is too high for either large tables or for high loads.
For our data warehouse with several billion row tables that are queried on every user login to do correlations between product purchases and views in order to recommend other products, changing that setting reduced the time it took to login from about three seconds down to less than 200 milliseconds. There's a good reason Oracle and Microsoft default to a looser transaction isolation setting in order to try to make their databases appear more performant.